Method and apparatus for configuring or activating various types of gaps in wireless communication system

ABSTRACT

The method includes receiving, by the terminal from a base station the RRCReconfiguration includes a one or more gap configuration and a MAC-CellGroupConfig and a one or more uplink bandwidth part configuration, each of the one or more gap configuration includes an identifier of the gap, triggering a Scheduling Request for a first MAC CE if the first MAC CE has been triggered and not cancelled and if uplink shared channel resources are not available for a new transmission, performing, by the terminal, Scheduling Request transmission based on a specific first configuration and a specific second configuration and transmitting, by the terminal to the base station to request activation of a first gap, the first MAC CE, wherein the specific first configuration is the first configuration corresponding to the first identifier1 and the specific second configuration is the second configuration associated with the specific first configuration.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to and the benefit of Korean PatentApplication No. filed on Jun. 9, 2022, the disclosure of which isincorporated herein by reference in its entirety.

BACKGROUND Technical Field

The present disclosure relates to configuring or activating varioustypes of gaps in wireless communication system.

Related Art

To meet the increasing demand for wireless data traffic since thecommercialization of 4th generation (4G) communication systems, the 5thgeneration (5G) system is being developed. For the sake of high, 5Gsystem introduced millimeter wave (mmW) frequency bands (e. g. 60 GHzbands). In order to increase the propagation distance by mitigatingpropagation loss in the 5G communication system, various techniques areintroduced such as beamforming, massive multiple-input multiple output(MIMO), full dimensional MIMO (FD-MIMO), array antenna, analogbeamforming, and large-scale antenna. In addition, base station isdivided into a central unit and plurality of distribute units for betterscalability. To facilitate introduction of various services, 5Gcommunication system targets supporting higher data rate and smallerlatency.

As the uses of terminals diversify, the need to control the operation ofterminals by applying various gaps according to circumstances isemerging. For example, it is necessary to set a gap for measurement, agap for MUSIM operation, or a gap for transmission power control so thatthe operation of the terminal can proceed efficiently.

SUMMARY

Aspects of the present disclosure are to address problem of activatinggaps. The method includes transmitting to the base station via SRB1 aUECapabilityInformation, the UECapabilityInformation includes aType7GapInfo2 indicating support of low latency measurement gapactivation request and a Type7GapInfo1 indicating support of low latencymeasurement gap activation, transmitting to the LMF via SRB2 aProvideCapabilities, the ProvideCapabilities includes a Type7GapInfo3indicating support of low latency measurement gap activation, receivingfrom the base station a RRCReconfiguration, the RRCReconfigurationincludes a MAC-CellGroupConfig IE and one or more PUCCH-Config IEs and aMeasGapConfig IE, setting up measurement gaps and activating some ofthem, performing Gap operation during the activated gaps, starting toperform location measurements toward NR, generating a MAC subPDUrequesting activation of a measurement gap for positioning based on theresult of logical channel prioritization, transmitting L2 gap requestmessage or L3 gap request message, receiving L2 gap response message orL3 gap response message in response to the L2 gap request message or theL3 gap request message, activating measurement gaps in accordance withthe received message and performing Gap operation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram illustrating the architecture of an 5G system and aNG-RAN to which the disclosure may be applied;

FIG. 1B is a diagram illustrating a wireless protocol architecture in an5G system to which the disclosure may be applied;

FIG. 1C is a diagram illustrating an example of a bandwidth part;

FIG. 1D is a diagram illustrating an example of a search space and acontrol resource set;

FIG. 1E is a diagram illustrating various gaps;

FIG. 1F is a diagram illustrating gap patterns of various gaps;

FIG. 1G is a diagram illustrating ASN.1 structure of IE configuringvarious gaps;

FIG. 1H is a diagram illustrating ASN.1 structure of IE configuringType5Gap;

FIG. 2 is a diagram illustrating operations of a terminal and a basestation according to an embodiment of the present invention;

FIG. 3 is a flow diagram illustrating an operation of a terminal;

FIG. 4A is a block diagram illustrating the internal structure of a UEto which the disclosure is applied;

FIG. 4B is a block diagram illustrating the configuration of a basestation according to the disclosure.

DETAILED DESCRIPTION

Hereinafter, embodiments of the present invention will be described indetail with reference to the accompanying drawings. In addition, in thedescription of the present invention, if it is determined that adetailed description of a related known function or configuration mayunnecessarily obscure the gist of the present invention, the detaileddescription thereof will be omitted. In addition, the terms to bedescribed later are terms defined in consideration of functions in thepresent invention, which may vary according to intentions or customs ofusers and operators. Therefore, the definition should be made based onthe content throughout this specification.

The terms used, in the following description, for indicating accessnodes, network entities, messages, interfaces between network entities,and diverse identity information is provided for convenience ofexplanation. Accordingly, the terms used in the following descriptionare not limited to specific meanings but may be replaced by other termsequivalent in technical meanings.

In the following descriptions, the terms and definitions given in thelatest 3GPP standards are used for convenience of explanation. However,the present disclosure is not limited by use of these terms anddefinitions and other arbitrary terms and definitions may be employedinstead.

Table 1 lists the acronyms used throughout the present disclosure.

TABLE 1 Acronym Full name 5GC 5G Core Network ACK Acknowledgement AMAcknowledged Mode AMF Access and Mobility Management Function ARQAutomatic Repeat Request AS Access Stratum ASN.1 Abstract SyntaxNotation One BSR Buffer Status Report BWP Bandwidth Part CA CarrierAggregation CAG Closed Access Group CG Cell Group C-RNTI Cell RNTI CSIChannel State Information DCI Downlink Control Information DRB (user)Data Radio Bearer DRX Discontinuous Reception HARQ Hybrid AutomaticRepeat Request IE Information element LCG Logical Channel Group MACMedium Access Control MIB Master Information Block NAS Non-AccessStratum NG-RAN NG Radio Access Network NR NR Radio Access PBRPrioritised Bit Rate PCell Primary Cell PCI Physical Cell IdentifierPDCCH Physical Downlink Control Channel PDCP Packet Data ConvergenceProtocol PDSCH Physical Downlink Shared Channel PDU Protocol Data UnitPHR Power Headroom Report PLMN Public Land Mobile Network PRACH PhysicalRandom Access Channel PRB Physical Resource Block PSS PrimarySynchronisation Signal PUCCH Physical Uplink Control Channel PUSCHPhysical Uplink Shared Channel RACH Random Access Channel RAN RadioAccess Network RA-RNTI Random Access RNTI RAT Radio Access Technology RBRadio Bearer RLC Radip Link Control RNA RAN-based Notification Area RNAURAN-based Notification Area Update RNTI Radio Network TemporaryIdentifier RRC Radio Resource Control RRM Radio Resource Management RSRPReference Signal Received Power RSRQ Reference Signal Received QualityRSSI Received Signal Strength Indicator SCell Secondary Cell SCSSubcarrier Spacing SDAP Service Data Adaptation Protocol SDU ServiceData Unit SFN System Frame Number S-GW Serving Gateway SI SystemInformation SIB System Information Block SpCell Special Cell SRBSignalling Radio Bearer SRS Sounding Reference Signal SSB SS/PBCH blockSSS Secondary Synchronisation Signal SUL Supplementary Uplink TMTransparent Mode UCI Uplink Control Information UE User Equipment UMUnacknowledged Mode CRP Cell Reselection Priority

Table 2 lists the terminologies and their definition used throughout thepresent disclosure.

TABLE 2 Terminology Definition allowedCG- List of configured grants forthe corresponding logical channel. This List restriction applies onlywhen the UL grant is a configured grant. If present, UL MAC SDUs fromthis logical channel can only be mapped to the indicated configuredgrant configuration. If the size of the sequence is zero, then UL MACSDUs from this logical channel cannot be mapped to any configured grantconfigurations. If the field is not present, UL MAC SDUs from thislogical channel can be mapped to any configured grant configurations.allowedSCS- List of allowed sub-carrier spacings for the correspondinglogical List channel. If present, UL MAC SDUs from this logical channelcan only be mapped to the indicated numerology. Otherwise, UL MAC SDUsfrom this logical channel can be mapped to any configured numerology.allowed List of allowed serving cells for the corresponding logicalchannel. If ServingCells present, UL MAC SDUs from this logical channelcan only be mapped to the serving cells indicated in this list.Otherwise, UL MAC SDUs from this logical channel can be mapped to anyconfigured serving cell of this cell group. Carrier center frequency ofthe cell. frequency Cell combination of downlink and optionally uplinkresources. The linking between the carrier frequency of the downlinkresources and the carrier frequency of the uplink resources is indicatedin the system information transmitted on the downlink resources. CellGroup in dual connectivity, a group of serving cells associated witheither the MeNB or the SeNB. Cell A process to find a better suitablecell than the current serving cell reselection based on the systeminformation received in the current serving cell Cell A process to finda suitable cell either blindly or based on the stored selectioninformation Dedicated Signalling sent on DCCH logical channel betweenthe network and a signalling single UE. discardTimer Timer to controlthe discard of a PDCP SDU. Starting when the SDU arrives. Upon expiry,the SDU is discarded. F The Format field in MAC subheader indicates thesize of the Length field. Field The individual contents of aninformation element are referred to as fields. Frequency set of cellswith the same carrier frequency. layer Global cell An identity touniquely identifying an NR cell. It is consisted of identitycellIdentity and plmn-Identity of the first PLMN-Identity inplmn-IdentityList in SIB1. gNB node providing NR user plane and controlplane protocol terminations towards the UE, and connected via the NGinterface to the 5GC. Handover procedure that changes the serving cellof a UE in RRC_CONNECTED. Information A structural element containingsingle or multiple fields is referred as element information element. LThe Length field in MAC subheader indicates the length of thecorresponding MAC SDU or of the corresponding MAC CE LCID 6 bit logicalchannel identity in MAC subheader to denote which logical channeltraffic or which MAC CE is included in the MAC subPDU MAC-I MessageAuthentication Code—Integrity. 16 bit or 32 bit bit string calculated byNR Integrity Algorithm based on the security key and various freshinputs Logical a logical path between a RLC entity and a MAC entity.There are channel multiple logical channel types depending on what typeof information is transferred e.g. CCCH (Common Control Channel), DCCH(Dedicate Control Channel), DTCH (Dedicate Traffic Channel), PCCH(Paging Control Channel) Logical The IE LogicalChannelConfig is used toconfigure the logical channel Channel parameters. It includes priority,prioritisedBitRate, allowedServingCells, Config allowedSCS-List,maxPUSCH-Duration, logicalChannelGroup, allowedCG- List etc logical IDof the logical channel group, as specified in TS 38.321, which theChannel logical channel belongs to Group MAC CE Control Elementgenerated by a MAC entity. Multiple types of MAC CEs are defined, eachof which is indicated by corresponding LCID. A MAC CE and acorresponding MAC sub-header comprises MAC subPDU Master Cell in MR-DC,a group of serving cells associated with the Master Node, Groupcomprising of the SpCell (PCell) and optionally one or more SCells.maxPUSC Restriction on PUSCH-duration for the corresponding logicalH-Duration channel. If present, UL MAC SDUs from this logical channelcan only be transmitted using uplink grants that result in a PUSCHduration shorter than or equal to the duration indicated by this field.Otherwise, UL MAC SDUs from this logical channel can be transmittedusing an uplink grant resulting in any PUSCH duration. NR NR radioaccess PCell SpCell of a master cell group. PDCP The process triggeredupon upper layer request. It includes the entity initialization of statevariables, reset of header compression and manipulating reestablish- ofstored PDCP SDUs and PDCP PDUs. The details can be found in 5.1.2 ofment 38.323 PDCP The process triggered upon upper layer request. Whentriggered, suspend transmitting PDCP entity set TX_NEXT to the initialvalue and discard all stored PDCP PDUs. The receiving entity stop andreset t-Reordering, deliver all stored PDCP SDUs to the upper layer andset RX_NEXT and RX_DELIV to the initial value PDCP- The IE PDCP-Configis used to set the configurable PDCP parameters config for signallingand data radio bearers. For a data radio bearer, discardTimer,pdcp-SN-Size, header compression parameters, t-Reordering and whetherintegrity protection is enabled are configured. For a signaling radiobearer, t- Reordering can be configured PLMN ID the process that checkswhether a PLMN ID is the RPLMN identity Check or an EPLMN identity ofthe UE. Primary The MCG cell, operating on the primary frequency, inwhich the UE Cell either performs the initial connection establishmentprocedure or initiates the connection re-establishment procedure.Primary For dual connectivity operation, the SCG cell in which the UESCG Cell performs random access when performing the Reconfiguration withSync procedure. priority Logical channel priority, as specified in TS38.321. an integer between 0 and 7. 0 means the highest priority and 7means the lowest priority PUCCH a Secondary Cell configured with PUCCH.SCell Radio Logical path between a PDCP entity and upper layer (i.e.SDAP entity Bearer or RRC) RLC bearer RLC and MAC logical channelconfiguration of a radio bearer in one cell group. RLC bearer The lowerlayer part of the radio bearer configuration comprising the configur-RLC and logical channel configurations. ation RX_DELIV This statevariable indicates the COUNT value of the first PDCP SDU not deliveredto the upper layers, but still waited for. RX_NEXT This state variableindicates the COUNT value of the next PDCP SDU expected to be received.RX_ This state variable indicates the COUNT value following the COUNTREORD value associated with the PDCP Data PDU which triggeredt-Reordering. Serving For a UE in RRC_CONNECTED not configured withCA/DC there Cell is only one serving cell comprising of the primarycell. For a UE in RRC_CONNECTED configured with CA/ DC the term 'servingcells' is used to denote the set of cells comprising of the SpecialCell(s) and all secondary cells. SpCell primary cell of a master orsecondary cell group. Special For Dual Connectivity operation the termSpecial Cell refers to the Cell PCell of the MCG or the PSCell of theSCG, otherwise the term Special Cell refers to the PCell. SRB SignallingRadio Bearers″ (SRBs) are defined as Radio Bearers (RBs) that are usedonly for the transmission of RRC and NAS messages. SRB0 SRB0 is for RRCmessages using the CCCH logical channel SRB1 SRB1 is for RRC messages(which may include a piggybacked NAS message) as well as for NASmessages prior to the establishment of SRB2, all using DCCH logicalchannel; SRB2 SRB2 is for NAS messages and for RRC messages whichinclude logged measurement information, all using DCCH logical channel.SRB2 has a lower priority than SRB1 and may be configured by the networkafter AS security activation; SRB3 SRB3 is for specific RRC messageswhen UE is in (NG)EN-DC or NR-DC, all using DCCH logical channel SRB4SRB4 is for RRC messages which include application layer measurementreporting information, all using DCCH logical channel. Suitable A cellon which a UE may camp. Following criteria apply cell The cell is partof either the selected PLMN or the registered PLMN or PLMN of theEquivalent PLMN list The cell is not barred The cell is part of at leastone TA that is not part of the list of ″Forbidden Tracking Areas forRoaming″ (TS 22.011 [18]), which belongs to a PLMN that fulfils thefirst bullet above. The cell selection criterion S is fulfilled (i.e.RSRP and RSRQ are better than specific values t-Reordering Timer tocontrol the reordering operation of received PDCP packets. Upon expiry,PDCP packets are processed and delivered to the upper layers. TX_NEXTThis state variable indicates the COUNT value of the next PDCP SDU to betransmitted. UE Inactive UE Inactive AS Context is stored when theconnection is suspended ASContext and restored when the connection isresumed. It includes information below. the current KgNB and KRRCintkeys, the ROHC state, the stored QoS flow to DRB mapping rules, theC-RNTI used in the source PCell, the cellIdentity and the physical cellidentity of the source PCell, the spCellConfigCommon withinReconfiguration WithSync of the NR PSCell (if configured) and all otherparameters configured except for: parameters within ReconfigurationWithSync of the PCell; parameters within ReconfigurationWithSync of theNR PSCell, if configured; parameters within MobilityControlInfoSCG ofthe E-UTRA PSCell, if configured; servingCellConfigCommonSIB;

In the present invention, “trigger” or “triggered” and “initiate” or“initiated” may be used in the same meaning.

In the present invention, “radio bearers allowed for the second resumeprocedure”, “radio bearers for which the second resume procedure isset”, and “radio bearers for which the second resume procedure isenabled” may all have the same meaning.

FIG. 1A is a diagram illustrating the architecture of an 5G system and aNG-RAN to which the disclosure may be applied.

5G system consists of NG-RAN 1A-01 and 5GC 1A-02. An NG-RAN node iseither:

-   -   a gNB, providing NR user plane and control plane protocol        terminations towards the UE; or    -   an ng-eNB, providing E-UTRA user plane and control plane        protocol terminations towards the UE.

The gNBs 1A-05 or 1A-06 and ng-eNBs 1A-03 or 1A-04 are interconnectedwith each other by means of the Xn interface. The gNBs and ng-eNBs arealso connected by means of the NG interfaces to the 5GC, morespecifically to the AMF (Access and Mobility Management Function) and tothe UPF (User Plane Function). AMF 1A-07 and UPF 1A-08 may be realizedas a physical node or as separate physical nodes.

A gNB 1A-05 or 1A-06 or an ng-eNBs 1A-03 or 1A-04 hosts the functionslisted below.

-   -   Functions for Radio Resource Management such as Radio Bearer        Control, Radio Admission Control, Connection Mobility Control,        Dynamic allocation of resources to UEs in uplink, downlink and        sidelink(scheduling); and    -   IP and Ethernet header compression, uplink data decompression        and encryption of user data stream; and    -   Selection of an AMF at UE attachment when no routing to an MME        can be determined from the information provided by the UE; and    -   Routing of User Plane data towards UPF; and    -   Scheduling and transmission of paging messages; and    -   Scheduling and transmission of broadcast information (originated        from the AMF or O&M); and    -   Measurement and measurement reporting configuration for mobility        and scheduling; and    -   Session Management; and    -   QoS Flow management and mapping to data radio bearers; and    -   Support of UEs in RRC_INACTIVE state; and    -   Radio access network sharing; and    -   Tight interworking between NR and E-UTRA; and    -   Support of Network Slicing.

The AMF 1A-07 hosts the functions such as NAS signaling, NAS signalingsecurity, AS security control, SMF selection, Authentication, Mobilitymanagement and positioning management.

The UPF 1A-08 hosts the functions such as packet routing and forwarding,transport level packet marking in the uplink, QoS handling and thedownlink, mobility anchoring for mobility etc.

FIG. 1B is a diagram illustrating a wireless protocol architecture in an5G system to which the disclosure may be applied.

User plane protocol stack consists of SDAP 1B-01 or 1B-02, PDCP 1B-03 or1B-04, RLC 1B-05 or 1B-06, MAC 1B-07 or 1B-08 and PHY 1B-09 or 1B-10.Control plane protocol stack consists of NAS 1B-11 or 1B-12, RRC 1B-13or 1B-14, PDCP, RLC, MAC and PHY.

Each protocol sublayer performs functions related to the operationslisted in the table 3.

TABLE 3 Sub- layer Functions NAS authentication, mobility management,security control etc RRC System Information, Paging, Establishment,maintenance and release of an RRC connection, Security functions,Establishment, configuration, maintenance and release of SignallingRadio Bearers (SRBs) and Data Radio Bearers (DRBs), Mobility, QoSmanagement, Detection of and recovery from radio link failure, NASmessage transfer etc. SDAP Mapping between a QoS flow and a data radiobearer, Marking QoS flow ID (QFI) in both DL and UL packets. PDCPTransfer of data, Header compression and decompression, Ciphering anddeciphering, Integrity protection and integrity verification,Duplication, Reordering and in-order delivery, Out-of-order deliveryetc. RLC Transfer of upper layer PDUs, Error Correction through ARQ,Segmentation and re-segmentation of RLC SDUs, Reassembly of SDU, RLCre-establishment etc. MAC Mapping between logical channels and transportchannels, Multiplexing/demultiplexing of MAC SDUs belonging to one ordifferent logical channels into/from transport blocks (TB) deliveredto/from the physical layer on transport channels, Scheduling informationreporting, Priority handling between UEs, Priority handling betweenlogical channels of one UE etc. PHY Channel coding, Physical-layerhybrid-ARQ processing, Rate matching, Scrambling, Modulation, Layermapping, Downlink Control Information, Uplink Control Information etc.

A reduced capability UE or RedCap UE has lower performance than ageneral UE and is used in limited scenarios such as TOT. Compared to atypical terminal having a bandwidth of 100 MHz, a transmission/receptionspeed of several Gbps, and four or more Rx processing units (Rxbranches), RedCap terminals have a bandwidth of 20 MHz, atransmission/reception speed of several tens of Mbps, and two or less Rxprocessing units.

The present invention provides a method and apparatus for a RedCap UE toaccess a cell supporting RedCap, receive system information, and performnecessary operations. In particular, the terminal applies search space 0(Search Space 0, hereinafter SS #0) and control resource set 0 (ControlResource Set 0, hereinafter CORESET #0) in the initial bandwidth part(IBWP) to obtain system information.

FIG. 1C is a diagram illustrating an example of a bandwidth part.

With Bandwidth Adaptation (BA), the receive and transmit bandwidth of aUE need not be as large as the bandwidth of the cell and can beadjusted: the width can be ordered to change (e.g. to shrink duringperiod of low activity to save power); the location can move in thefrequency domain (e.g. to increase scheduling flexibility); and thesubcarrier spacing can be ordered to change (e.g. to allow differentservices). A subset of the total cell bandwidth of a cell is referred toas a Bandwidth Part (BWP) and BA is achieved by configuring the UE withBWP(s) and telling the UE which of the configured BWPs is currently theactive one.

FIG. 1C describes a scenario where 3 different BWPs are configured:

-   -   BWP1 with a width of 40 MHz and subcarrier spacing of 15 kHz;        1C-11 or 1C-19    -   BWP2 with a width of 10 MHz and subcarrier spacing of 15 kHz;        1C-13 or 1C-17    -   BWP3 with a width of 20 MHz and subcarrier spacing of 60 kHz.        1C-15

FIG. 1D is a diagram illustrating an example of a search space and acontrol resource set.

A plurality of SSs may be configured in one BWP. The UE monitors PDCCHcandidates according to the SS configuration of the currently activatedBWP. One SS consists of an SS identifier, a CORESET identifierindicating the associated CORESET, the period and offset of the slot tobe monitored, the slot unit duration, the symbol to be monitored in theslot, the SS type, and the like. The information may be explicitly andindividually configured or may be configured by a predetermined indexrelated to predetermined values.

One CORESET consists of a CORESET identifier, frequency domain resourceinformation, symbol unit duration, TCI status information, and the like.

Basically, it can be understood that CORESET provides frequency domaininformation to be monitored by the UE, and SS provides time domaininformation to be monitored by the UE.

CORESET #0 and SS #0 may be configured in the IBWP. One CORESET and aplurality of SSs may be additionally configured in the IBWP. Uponreceiving the MIB 1D-01, the UE recognizes CORESET #0 1D-02 and SS #01D-03 for receiving SIB1 using predetermined information included in theMIB. The UE receives SIB1 1D-05 through CORESET #0 1D-02 and SS #01D-03. In SIB 1, information constituting CORESET #0 1D-06 and SS #01D-07 and information constituting another CORESET, for example, CORESET#n 1D-11 and SS #m 1D-13 may be included.

The terminal receives necessary information from the base station beforethe terminal enters the RRC_CONNECTED state, such as SIB2 reception,paging reception, and random access response message reception by usingthe CORESETs and SS s configured in SIB . CORESET #0 1D-02 configured inMIB and CORESET #0 1D-06 configured in SIB1 may be different from eachother, and the former is called a first CORESET #0 and the latter iscalled a second CORESET #0. SS #0 1D-03 configured in MIB and SS #01D-07 configured in SIB1 may be different from each other, and theformer is referred to as a first SS #0 and the latter is referred to asa second SS #0. SS #0 and CORESET #0 configured for the RedCap terminalare referred to as a third SS#0 and a third CORESET#0. The first SS #0,the second SS #0, and the third SS #0 may be the same as or differentfrom each other. The first CORESET #0, the second CORESET #0, and thethird CORESET #0 may be the same as or different from each other. SS #0and CORESET #0 are each indicated by a 4-bit index. The 4-bit indexindicates a configuration predetermined in the standard specification.Except for SS #0 and CORESET #0, the detailed configuration of theremaining SS and CORSESET is indicated by each individual informationelement.

When the RRC connection is established, additional BWPs may beconfigured for the UE.

A Serving Cell may be configured with one or multiple BWPs.

UE can be configured with one or more DL BWPs and one or more UL BWPs ina serving cell. If the serving cell operates in paired spectrum (i.e.,FDD band), the number of DL BWPs and the number of UL BWPs can bedifferent. If the serving cell operates in unpaired spectrum (i.e., TDDband), the number of DL BWPs and the number of UL BWPs is same.

SIB1 includes a DownlinkConfigCommonSlB and a UplinkConfigCommonSlB anda tdd-UL-DL-ConfigurationCommon.

TDD-UL-DL-ConfigurationCommon is cell specific TDD UL/DL configuration.It consists of subfields such as referenceSubcarrierSpacing, pattern1,and pattern2.

ReferenceSubcarrierSpacing is the reference SCS used to determine thetime domain boundary in the UL-DL pattern.

Pattern1and pattern2 are TDD Uplink Downlink Pattern. It consists ofsubfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots,nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

DL-UL-TransmissionPeriodicity indicates the period of the DL-UL pattern.

NRofDownlinkSlots indicates the number of consecutive full DL slots ineach DL-UL pattern.

NRofDownlinkSymbols indicates the number of consecutive DL symbols fromthe beginning of the slot following the last full DL slot.

NRofUplinkSlots indicates the number of consecutive full UL slots ineach DL-UL pattern.

NRofUplinkSymbols indicates the number of consecutive UL symbols at thelast time point of a slot preceding the first full UL slot.

Slots between the last full DL slot and the first full UL slot areflexible slots. full UL slot is also called static UL slot. UL slot inthis disclosure is static UL slot.

DownlinkConfigCommonSlB includes BWP-DownlinkCommon IE for initial DLBWP. UplinkConfigCommonSlB includes BWP-UplinkCommon IE for initial ULBWP. BWP-id of initialDownlinkBWP is 0.

A RRCReconfiguration message includes one or more BWP-Downlink and oneor more BWP-Uplink and a firstActiveDownlinkBWP-Id and abwp-InactivityTimer and a defaultDownlinkBWP-Id and aBWP-DownlinkDedicated for the initial DL BWP.

A BWP-Downlink IE includes a bwp-Id and a BWP-DownlinkCommon and aBWP-DownlinkDedicated.

A BWP-Uplink IE includes a bwp-Id and a BWP-UplinkCommon and aBWP-UplinkDedicated.

The bwp-Id is an integer between 0 and 4. bwp-Id 0 is used only for theBWP indicated in SIB1. bwp-Id1˜4 can be used for the BWPs indicated inthe RRCReconfiguration message.

BWP-DownlinkCommon IE includes following information: Frequency domainlocation and bandwidth of this bandwidth part, subcarrier spacing to beused in this BWP, cell specific parameters for the PDCCH of this BWP,cell specific parameters for the PDSCH of this BWP.

BWP-UplinkCommon IE includes following information: Frequency domainlocation and bandwidth of this bandwidth part, subcarrier spacing to beused in this BWP, cell specific parameters for the PUCCH of this BWP,cell specific parameters for the PUSCH of this BWP, Configuration ofcell specific random access parameters.

BWP-DownlinkDedicated is used to configure the dedicated (UE specific)parameters of a downlink BWP. It includes cell specific parameters forthe PDCCH of this BWP, cell specific parameters for the PDSCH of thisBWP.

The BWP-UplinkDedicated is used to configure the dedicated (UE specific)parameters of an uplink BWP.

FirstActiveDownlinkBWP-Id contains the ID of the DL BWP to be activatedupon performing the RRC (re-)configuration.

DefaultDownlinkBWP-Id is the ID of the downlink bandwidth part to beused upon expiry of the BWP inactivity timer.

BWP-InactivityTimer is the duration in ms after which the UE falls backto the default Bandwidth Part

RRCReconfiguration message includes one or more SCellConfig IEs. ASCellConfig IE is used to configure a secondary cell. A SCellConfig IEcan includes a serving cell index and a serving cell configuration and asCellDeactivationTimer.

FIG. 1E is a diagram illustrating various gaps.

In this disclosure six gaps are defined: Type1Gap, Type2Gap, Type3Gap,Type4Gap, Type5Gap and Type6Gap and Type7Gap.

Type1Gap is used for RRM measurement on all FR1 frequencies or on allFR2 frequencies or on all frequencies. Type1Gap is always activated onceit is configured. During a Type1Gap 1E-03, UE performs gap operation1.

Type2Gap is used for RRM measurement on all frequencies. Type2Gap isactivated only when an associated BWP is activated (or deactivated).During a Type2Gap 1E-03, UE performs gap operation1-1. A Type2Gap can becalled preconfigured gap.

Type3Gap is used for RRM measurement on specific frequency (orfrequencies). Type3Gap is always activated once it is configured. Duringa Type3Gap 1E-03, UE performs gap operation)-1. A Type3Gap can be calledconcurrent gap. A type3Gap is associated with a frequency if the ID ofthe type3Gap is indicated in the measurement object of the frequency.

One or more type3Gaps can be associated with a measurement object (i.e.a configuration information for a measurement object can includes aplurality of measGapId(s)). In this case, the plurality of type3Gaps areused simultaneously for measurement on the frequency associated with themeasurement object. It is useful in circumstances where adjacentneighboring cells are not synchronized with each other.

Type4Gap is used for RRM measurement on all FR1 frequencies or on allFR2 frequencies or on all frequencies. UE performs data activity likeDL-SCH reception during Type4Gap. A Type4Gap 1E-05 consists of twointerruption periods 1E-09 and one measurement period 1E-07. During theinterruption periods, UE performs gap operation 2. During themeasurement period 1E-07, UE performs gap operation 3. A Type4Gap can becalled NCSG (Network Controlled Small Gap).

Type5Gap is used for activity in the other USIM. During a Type5Gap1E-11, UE performs gap operation4. A Type5Gap can be called MUSIM Gap.

Type6Gap is used for power management. During a Type6Gap 1E-13, UEperforms gap operation6. Type6Gap starts with an UL slot. UE determinesthe UL slot based on the tdd-UL-DL-ConfigurationCommon.

Type7Gaps are associated with the measurement of PRS for RSTD, UE-RxTxTime Difference, PRS-RSRP and PRS-RSRPP. Type7Gaps are deactivatedinitially when configured. Type7Gaps are activated by the base stationbased on the request from the UE. Type7Gap is a preconfigured MG for PRSmeasurements

FIG. 1F is a diagram illustrating gap patterns of various gaps.

Type1Gap and Type3Gap and Type4Gap and Type6Gap are periodicallyoccurring once they are configured. Type2Gap and Type7Gap areperiodically occurring once configured and activated. Type5Gap is eitherperiodically occurring or aperiodically occurring once configured.

The pattern of periodic gaps is controlled by an offset parameter and agap repetition period parameter and a gap length parameter. For example,when offset is 24 and gap repetition period is 40 ms and gap length is 4ms, the first gap(1F-11) occurs at subframe #4 of SFN 22 and continues 4msec. The second gap(1F-13) occurs at subframe #4 of SFN 25 andcontinues 4 msec and so on.

The pattern of aperiodic gaps is controlled by offset parameter and gaprepetition period parameter and gap length parameter and gap numberparameter. For example, when offset is 5220 and gap repetition period is64 ms and gap length is 32 ms, the first gap 1F-15 occurs at subframe #0of SFN 522 and continues 32 msec. The second gap 1F-17 occurs atsubframe #4 of SFN 528 and continues 32 msec. Since gap number is 2,only two gaps occur.

To configure Type1Gap or Type2Gap or Type3Gap or Type4Gap or Type7Gap,MeasGapConfig IE is used. MeasGapConfig IE is included in MeasConfig IE.MeasConfig IE is included in RRCReconfiguration message.

MeasGapConfig IE may include a gapFR2 field and a gapFR1 field and agapUE field and a PosMeasGapPreConfigToAddModList field and aPosMeasGapPreConfigToReleaseList field and a gapToAddModList field and agapToReleaseList field.

To configure Type5Gap, Musim-GapConfig IE is used. Musim-GapConfig IE isincluded in RRCReconfiguration message.

Musim-GapConfig IE can includes musim-GapConfigToRemoveList andmusim-GapConfigToAddModList. musim-GapConfigToAddModList consist ofplurality of musim-GapConfigToAddMod.

To configure Type6Gap, Type6GapConfig IE is used. Type6GapConfig IE isincluded in RRCReconfiguration message.

FIG. 2 is a diagram illustrating the operations for gap configuration.

In 2A-11, UE transmits GNB UECapabilityInformation message.UECapabilityInformation message includes following gap relatedcapability information: gap-request-capability-information,gap-configuration-capability-information.

gap-request-capability-information includes following information:NeedForGap-Reporting, musim-NeedForGap-Reporting

UE can request Type1Gap and Type2Gap and Type3Gap and Type4Gap bytransmitting either RRCReconfigurationComplete message orRRCResumeComplete message or LocationMeasurementInfo.

UE can request Type5Gap by transmitting UEAssistanceInformation.

For UE to request gap by transmitting RRCReconfigurationComplete orRRCResumeComplete or UEAssistanceInformation, GNB needs to configure UEto request gap. GNB determines it based on reported capability. UE canrequest gap by LocationMeasurementInfo without any prior configuration.

NeedForGap-Reporting indicates whether the UE supports reporting themeasurement gap requirement information for NR target in the UE responseto a network configuration RRC message. It is enumerated with a singlevalue of “support”. It is per UE capability. A single IE can be presentin UECapability for NR. Absence of the IE indicates the feature is notsupported by the UE. Presence of the IE indicates the feature issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

Musim-NeedForGap-Reporting indicates whether the UE supports reportingthe gap requirement information for MUSIM. It is enumerated with asingle value of “support”. It is per UE capability. A single IE can bepresent in UECapability for NR. Absence of the IE indicates the featureis not supported by the UE. Presence of the IE indicates the feature issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

NeedForGap-Reporting indicates the capability related to type1Gap andtype2Gap and type3Gap and type4Gap. If NeedForGap-Reporting andsupportType2Gap are reported, UE supports reporting the measurement gaprequirement information for Type2Gap. If NeedForGap-Reporting andsupportType4Gapare reported, UE supports reporting the measurement gaprequirement information for Type4Gap. If NeedForGap-Reporting isreported, UE supports reporting the measurement gap requirements forType1Gap and Type3 Gap.

UE does not report capability on whether the UE support reporting themeasurement gap requirement information in the UE initiated RRC message(i.e., LocationMeasurementInfo).

GAP-configuration-capability-information includes following information:supportedGapPattern, supportType2Gap, supportType4Gap, supportType5Gap,supportType6Gap and supportedGapCombination and Type7GapInfo1 andType7GapInfo2.

SupportedGapPattern indicates measurement gap pattern(s) optionallysupported by the UE. It is a bit string with 22 bits. Theleading/leftmost bit (bit 0) corresponds to the gap pattern 2, the nextbit corresponds to the gap pattern 3 and so on. A gap pattern is definedby a Gap Length and a Repetition Period. It is per UE capability. Thesupported gap patterns are supported by the UE in FR1 and in FR2 and inFDD and in TDD.

SupportType2Gap indicates whether the UE supports Type2Gap (i.e., gapactivated and deactivated depending on which BWP is activated; DL BWPdependent gap). It is per band capability. One or more IEs can bepresent in UECapability for NR. Absence of the IE in a band informationindicates the feature is not supported by the UE in the correspondingband. Presence of the IE indicates the feature is supported by the UE inthe corresponding band.

Alternatively, it can be per UE capability. In this case, a single IEcan be present in UECapability for NR. Absence of the IE indicates thefeature is not supported by the UE. Presence of the IE indicates thefeature is supported by the UE in FR1 and in FDD and in TDD. To indicatewhether UE support Type2Gap in FR2, additional capability information isused.

SupportType4Gap indicates whether the UE supports Type4Gap (i.e., gapconsists of interruption period and measurement period; gap whereinterruption on data activity occurs in the beginning of a gap and inthe end of a gap; gap where measurement is performed withoutinterruption on data activity in the middle of the gap). It is per bandcapability. One or more IEs can be present in UECapability for NR.Absence of the IE in a band information indicates the feature is notsupported by the UE in the corresponding band. Presence of the IEindicates the feature is supported by the UE in the corresponding band.

Alternatively, it can be per UE capability. In this case, a single IEcan be present in UECapability for NR. Absence of the IE indicates thefeature is not supported by the UE. Presence of the IE indicates thefeature is supported by the UE in FR1 and in FR2 and in FDD and in TDD.

SupportType5Gap indicates whether the UE supports Type5Gap.Alternatively, it indicates whether UE supports MUSIM assistanceinformation reporting. It is per UE capability. A single IE can bepresent in UECapability for NR. Absence of the IE indicates the featureis not supported by the UE. Presence of the IE indicates the feature issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

SupportType6Gap indicates whether the UE supports Type6Gap. It is per FRcapability. two IEs can be present in UECapability for NR. Absence ofthe IE for FR2 indicates the feature is not supported by the UE in theFR2. Presence of the IE for FR2 indicates the feature is supported bythe UE in the FR and in TDD. Presence of the IE for FR1 indicates thefeature is supported by the UE in the FR and in TDD and in FDD.

SupportedGapCombination indicates gap combinations supported by the UEamong predefined gap combinations. It is a bit string with a predefinedsize. The predefined size is equal to the number of predefined gapcombinations optionally supported. The leading/leftmost bit (bit 0)corresponds to the optional gap combination with the lowest index, thenext bit corresponds to the optional gap combination with the nextlowest index and so on. A gap combination consists of gap combinationidentifier (or index) and number of per-FR1 gaps and number of per-FR2gaps and number of per-UE gaps. This IE indicates the number ofmeasurement gaps simultaneously supported by the UE. It is per UEcapability. The supported gap combinations are supported by the UE inFR1 and in FR2 and in FDD and in TDD.

A gap combination consists of gap combination identifier (or index) andnumber of per-FR1 gaps and number of per-FR2 gaps and number of per-UEgaps. Among the predefined gap combinations, some predefined gapcombinations are mandatorily supported by the UE. Some predefined gapcombinations are optionally supported by the UE. supportedGapCombinationindicates which optional gap combinations are supported by the UE.

Example is shown in the table below. The range of the integer is between0 and 2 (i.e., the highest value is 2 and the lowest value is 0; themaximum number of simultaneous gaps per FR is 2).

TABLE 4 # of simultaneous MG Per- Per- Per- Index FR1 FR2 UE . . . . . .. . . . . . n integer1 integer2 integer3 n + 1 integer4 integer5integer6 . . . . . . . . . . . .

Type7GapInfo1, if present, indicates UE supports preconfiguration of MGsin RRC signalling for PRS measurements and the use of DL MAC CE from thegNB to activate/deactivate the preconfigured MG for PRS measurements.This capability is related to DL MAC CE based type7Gap activation.

Type7GapInfo2, if present, indicates UE supports preconfiguration of MGsin RRC signalling for PRS measurements and the use of UL MAC CE torequest the activation/deactivation of the preconfigured MG for PRSmeasurements. The UE can include this field only if the UE supportsType7GapInfo1. This capability is related to UL MAC CE based type7Gapactivation request.

Type7GapInfo1 is reported to GNB only since MG activation using DL MACCE lies in GNB's responsibility.

Type7GapInfo2 is reported to GNB in a RRC message and to LMF in a LPPmessage since LMF needs to provide GNB the relevant information if UEsupports measurement gap activation request.

Alternatively, Type7GapInfo1 and Type7GapInfo2 are included in aUECapabilityInformation RRC message and Type7GapInfo3 is included in aProvideCapabilities LPP message.

Type7GapInfo3 , if present, indicates that the target device (i.e., theUE) supports low latency measurement gap activation request for DL-PRSmeasurements. This capability is related to both UL MAC CE basedtype7Gap activation request and DL MAC CE based type7Gap activationsince supporting measurement gap activation request implies supportingmeasurement gap activation.

UE supporting only Type7GapInfo1 (i.e. UE who included onlyType7GapInfo1 in UECapabilityInformation) does not include Type7GapInfo3in ProvideCapabilities LPP message.

UE supporting both Type7GapInfo1 and Type7GapInfo2 (i.e. UE who includedboth Type7GapInfo1 and Type7GapInfo2 in UECapabilityInformation)includes Type7GapInfo3 in ProvideCapabilities LPP message.

DL/UL MAC CE processing is quicker than DL/UL RRC message because MAC CEis simpler to decode/encode. In that sense, use of DL/UL MAC CE can beconsidered low latency activity.

The ProvideCapabilities LPP message is transmitted to the LMF throughGNB when LMF requests it. It is often before location service isstarted.

UECapabilityInformation is transmitted via SRB1 and ProvideCapabilitiesLPP message is transmitted in SRB2.

Based on reported UE capabilities, GNB determines configurations to beapplied to the UE.

BWP-SwitchingDelay defines whether the UE supports DCI and timer basedactive BWP switching delay type1 or type2. It indicates one of type1 andtype2. It is per UE capability. The indicated bwp-SwitchingDelay issupported by the UE in FR1 and in FR2 and in FDD and in TDD.

In 2A-13, GNB transmits UE first RRC message. first RRC message includesconfiguration information for gap request. Configuration information forgap request includes one of followings: needForGapsConfigNR,needForGapsConfigNR2, needForGapsConfigNR3, musim-AssistanceConfig andneedFortype6GapConfig. needForGapsConfigNR and needForGapsConfigNR2 andneedForGapsConfigNR3 can be included in RRCReconfiguration message or inRRCResume message. musim-AssistanceConfig and needForType6GapConfig canbe included in otherConfig in RRCReconfiguration message.

NeedForGapsConfigNR contains configuration related to the reporting ofmeasurement gap requirement information. needForGapsConfigNR includes arequestedTargetBandFilterNR. The requestedTargetBandFilterNR indicatesthe target NR bands that the UE is requested to report the gaprequirement information. The requestedTargetBandFilterNR consists of oneor more frequency band indicators.

NeedForGapsConfigNR2 indicates whether UE is allowed to provideNeedForGapsInfoNR2. This IE is enumerated with a single value “True”. Ifthis IE is absent, UE is not allowed to provide NeedForGapsInfoNR2. Ifthis IE is present, UE is allowed to provide NeedForGapsInfoNR2.

NeedForGapsConfigNR3 indicates whether UE is allowed to provideNeedForGapInfoNR3. This IE is enumerated with a single value “True”. Ifthis IE is absent, UE is not allowed to provide NeedForGapInfoNR3. Ifthis IE is present, UE is allowed to provide NeedForGapInfoNR3.

If RRCReconfiguration message or RRCResume message includesneedForGapInfoNR or if needForGapInfoNR has been setup and has not beenreleased, needForGapsConfigNR2 and needForGapInfoNR3 can be included inthe RRCReconfiguration message or in the RRCResume message.

NeedForType6GapConfig indicates whether UE is configured to request fortype6gap activation/deactivation and to provide preferred type6Gappattern. This IE is enumerated with a single value “True”. If this IE isabsent, UE is not configured to provide preferred type6Gap pattern (orpreference on type6Gap). If this IE is present, UE is configured toprovide preferred type6Gap pattern(or preference on type6Gap).

Musim-AssistanceConfig includes a gapRequestProhibitTimer field. thegapRequestProhibitTimer is enumerated with values. Each valuecorresponds to length of duration in a unit of seconds.

In 2A-15, UE checks whether gap-request is needed. UE generates gaprequest information if so.

UE consider itself to be configured to provide the measurement gaprequirement information of NR target bands, if the RRCReconfigurationmessage includes the needForGapInfoNR and if needForGapInfoNR is set tosetup.

UE consider itself to be configured to provide the measurement gaprequirement information of NR target bands, if the RRCResume messageincludes the needForGapInfoNR and if needForGapInfoNR is set to setup.

Condition-group-1 is fulfilled, if the RRCReconfiguration message wasreceived via SRB1 but not within mrdc-SecondaryCellGroup or E-UTRARRCConnectionReconfiguration or E-UTRA RRCConnectionResume, and if theUE is configured to provide the measurement gap requirement informationof NR target bands, and if the RRCReconfiguration message includes theneedForGapsConfigNR.

Condition-group-2 is fulfilled if the RRCResume message includes theneedForGapsConfigNR.

If condition-group-1 is fulfilled or condition-group-2 is fulfilled, UEinclude the needForGapsInfoNR in the second RRC message and set thecontents as follows:

UE includes intraFreq-needForGap and set the gap requirement informationof intra-frequency measurement for each NR serving cell. UE sets eithergap or no-gap for each serving cell.

UE includes an entry in interFreq-needForGap and set the gap requirementinformation for that band if requestedTargetBandFilterNR is configured,for each supported NR band that is also included inrequestedTargetBandFilterNR. UE sets either gap or no-gap for eachsupported NR band.

If condition-group-1 is fulfilled and the RRCReconfiguration messageincludes needForGapsInfoNR2, or if condition-group-2 is fulfilled andthe RRCResume message includes needForGapsInfoNR2, UE includes theneedForGapsInfoNR2 in the second RRC message and set the contents asfollows:

The second RRC message is RRCReconfigurationComplete ifcondition-group-1 was fulfilled. The second message is RRCResumeCompleteif condition-group-2 was fulfilled.

UE includes intraFreq-needForGap2 and set the interruption requirementinformation (i.e., whether ncsg is required) of intra-frequencymeasurement for each NR serving cell. UE sets either ncsg or no-ncsg foreach serving cell.

UE includes an entry in interFreq-needForGap2 and set the interruptionrequirement information for that band if requestedTargetBandFilterNR isconfigured, for each supported NR band that is also included inrequestedTargetBandFilterNR. UE sets either ncsg or no -nscg for eachsupported NR band.

If condition-group-1 is fulfilled and if the RRCReconfiguration messageincludes needForGapsInfoNR3 and if only one serving cell is configuredto the UE (i.e., UE is not configured with carrier aggregation; UE isconfigured with single carrier) as consequence of reconfiguration, UEincludes the needForGapsInfoNR3 in the second RRC message and set thecontents as follows:

UE includes bwpNeedForGap and set the gap requirement information foreach DL BWP of PCell (or SpCell).

If condition-group-2 is fulfilled and if the RRCResume message includesneedForGapsInfoNR3 and if only one serving cell is configured to the UE(i.e., UE is not configured with carrier aggregation; UE is configuredwith single carrier) as consequence of RRC connection resumption, UEincludes the needForGapsInfoNR3 in the second RRC message and set thecontents as follows:

UE includes bwpNeedForGap and set the gap requirement information foreach DL BWP of PCell (or SpCell).

UE consider itself to be configured to provide MUSIM assistanceinformation, if the received otherConfig includes musim-AssistanceConfigand if musim-AssistanceConfig is set to setup.

If UE is configured to provide MUSIM assistance information and if UEneeds the Type5Gap, UE initiate transmission of UEAssistanceInformationas follows:

If UE has a preference for Type5Gap, UE includes musim-GapRequestList inthe UEAssistanceInformation.

If UE determines that type6Gap request is needed, UE generates a type6request MAC CE. The type6 request MAC CE can includes an information onratio between the length of type6Gap and the repetition period oftype6Gap. If transmission power sum should be decreased a lot, higherratio is reported.

Alternatively, if UE is configured to provide its preference on type6Gapand if the UE did not transmit a UEAssistanceInformation withtype6Gap-Preference since it was configured to provide its preference ontype6Gap information, UE initiates transmission ofUEAssistanceInformation.

If UE is configured to provide its preference on type6Gap and if the UEtransmitted a UEAssistanceInformation with type6Gap-Preference since itwas configured to provide its preference on type6Gap and if the currenttype6Gap preference is different from the one indicated in the lasttransmission of the UEAssistanceInformation, UE initiates transmissionof UEAssistanceInformation.

If UE is configured to provide its preference on type6Gap and if the UEtransmitted a UEAssistanceInformation with type6Gap-Preference since itwas configured to provide its preference on type6Gap and if type6Gap isnot required, UE initiates transmission of UEAssistanceInformation.

If transmission of the UEAssistanceInformation message is initiated toprovide preference on type6Gap, UE includes Type6Gap-Preference IE inthe UEAssistanceInformation.

If Type6Gap is required, UE includes a Type6Gap-bitmap in theType6Gap-Preference IE.

If Type6Gap is not required, UE does not include a Type6Gap-bitmap inthe Type6Gap-Preference IE.

UE transmits the UEAssistanceInformation to the base station.

NeedForGapsInfoNR consists of intraFreq-needForGap andinterFreq-needForGap. NeedForGapsInfoNR is used to indicate themeasurement gap requirement information of the UE for NR target bands.

IntraFreq-needForGap field includes NeedForGapsIntraFreqlist IE. Thisfield indicates the measurement gap requirement information for NRintra-frequency measurement.

NeedForGapsIntraFreqlist consists of one or more NeedForGapsIntraFreq.NeedForGapsIntraFreq consists of servCellId and gapIndicationIntra.servCellId indicates the serving cell which contains the target SSB(associated with the initial DL BWP) to be measured. gapIndicationIntraindicates whether measurement gap is required for the UE to performintra-frequency SSB based measurements on the concerned serving cell.“gap” indicates that a measurement gap is needed if any of the UEconfigured BWPs do not contain the frequency domain resources of the SSBassociated to the initial DL BWP. “no-gap” indicates a measurement gapis not needed to measure the SSB associated to the initial DL BWP forall configured BWPs.

InterFreq-needForGap field includes NeedForGapsBandlistNR. This fieldindicates the measurement gap requirement information for NRinter-frequency measurement.

NeedForGapsBandlistNR consists of one or more NeedForGapsNR.NeedForGapsNR consists of bandNR and gapIndication. bandNR indicates theNR target band to be measured. gapIndication indicates whethermeasurement gap is required for the UE to perform SSB based measurementson the concerned NR target band while NR-DC or NE-DC is not configured.The UE determines this information based on the resultant configurationof the RRCReconfiguration or RRCResume message that triggers thisresponse. Value gap indicates that a measurement gap is needed, valueno-gap indicates a measurement gap is not needed.

NeedForGapsInfoNR2 consists of intraFreq-needForGap2 andinterFreq-needForGap2. NeedForGapsInfoNR2 is used to indicate theinterruption requirement information of the UE for NR target bands.Alternatively, this IE is used to indicate type4Gap (i.e., networkcontrolled small gap) requirement information of the UE for NR targetbands.

IntraFreq-needForGap2 field includes one or more gapIndication2 IEs.Each of one or more gapIndication2 IE in intraFreq-needForGap2 indicatesthe interruption requirement (or type4Gap requirement) information forNR intra-frequency measurement with respect to a specific serving cell.

InterFreq-needForGap2 field includes one or more gapIndication2 IEs.Each of one or more gapIndication2 IE in interFreq-needForGap2 indicatesthe interruption requirement (or type4Gap requirement) information forNR inter-frequency measurement with respect to a specific frequencyband.

GapIndication2 is enumerated with three values: “gap” and “ncsg” and“nogap-noncsg”.

If gapIndication2 is set to “ncsg”for a serving cell, ncsg (or type4Gap)is required for the UE to perform intra-frequency SSB measurement on theconcerned serving cell.

If gapIndication2 is set to “ncsg” for a frequency band, ncsg (ortype4Gap) is required for the UE to perform SSB based measurement on theconcerned target band.

If gapIndication2 is set to “gap”for a serving cell, type1Gap ortype2Gap or type3Gap is required for the UE to perform intra-frequencySSB measurement on the concerned serving cell.

If gapIndication2 is set to “gap” for a frequency band, type1Gap ortype2Gap or type3Gap is required for the UE to perform SSB basedmeasurement on the concerned target band.

If gapIndication2 is set to “nogap-noncsg”for a serving cell, neithertype1Gap nor type2Gap nor type3Gap nor type4Gap is required for the UEto perform intra-frequency SSB measurement on the concerned servingcell.

If gapIndication2 is set to “nogap-noncsg” for a frequency band, neithertype1Gap nor type2Gap nor type3Gap nor type4Gap is required for the UEto perform SSB based measurement on the concerned target band.

NeedForGapsInfoNR3 consists of a bwpNeedForGap. NeedForGapsInfoNR3 isused to indicate the measurement gap requirement information of DL BWPsconfigured for the UE.

BWPNeedForGap field includes a BIT STRING. The size of the BIT STRING isequal to the number of DL BWPs configured for the UE in the PCell.Alternatively, the size of the BIT STRING is fixed to a specific valuesuch as 4.

The leading/leftmost bit (bit 0) corresponds to the DL BWP with lowestindex (or BWP 0). The next bit corresponds to the DL BWP with nextlowest index (or BWP 1) and so on. Value 1 indicates type2Gap isrequired for the UE to perform measurement in the corresponding DL BWP.Value 0 indicates type2Gap is not required for the UE to performmeasurement in the corresponding DL BWP. The measurement can beintra-frequency measurement based on SSB or intra-frequency measurementbased on CSI-RS.

MUSIM-GapRequestList consists of MUSIM-GapRequestList IE. This IEindicate the MUSIM gap (i.e., type5Gap) requirement information.

MUSIM-GapRequestList IE includes one or two or threeMUSIM-GapRequestInfo IE. The reason to limit to three in maximum isbecause configuring a single aperiodic gap and two periodic gaps is acommon scenario with consideration of MUSIM gap usage.

MUSIM-GapRequestInfo includes RequestedMusim-GapType andRequestedMusim-GapOffset and RequestedMusim-GapLength andRequestedMusim-GapRepetitionPeriod and RequestedMusim-GapNumber.

RequestedMusim-GapType is enumerated with a single value of “aperiodic”.If this IE is present in MUSIM-GapRequestInfo and this IE indicates“aperiodic”, aperiodic musim-gap is required. If this IE is absent inMUSIM-GapRequestInfo, periodic musim-gap is required.

Alternatively, RequestedMusim-GapType is enumerated with a single valueof “periodic”. If this IE is present in MUSIM-GapRequestInfo and this IEindicates “periodic”, periodic musim-gap is required. If this IE isabsent in MUSIM-GapRequestInfo, aperiodic musim-gap is required.

Alternatively, if RequestedMusim-GapRepetitionPeriod is present inMUSIM-GapRequestInfo, periodic musim-gap is required. If this IE isabsent in MUSIM-GapRequestInfo, aperiodic musim-gap is required.

Alternatively, if RequestedMusim-GapRepetitionPeriod inMUSIM-GapRequestInfo is set to a specific value like 0, aperiodicmusim-gap is required. If RequestedMusim-GapRepetitionPeriod inMUSIM-GapRequestInfo is set to other value, periodic musim-gap isrequired.

Alternatively, if RequestedMusim-GapNumber is present inMUSIM-GapRequestInfo, aperiodic musim-gap is required. If this IE isabsent in MUSIM-GapRequestInfo, periodic musim-gap is required.

RequestedMusim-GapOffset1 and RequestedMusim-GapOffset2 indicate thepreferred musim-Gap starting time point.

RequestedMusim GapLength1 and RequestedMusim-GapLength2 indicate thepreferred musim-Gap length.

RequestedMusim-GapRepetitionPeriod1 andRequestedMusim-GapRepetitionPeriod2 indicate the preferred repetitionperiod.

RequestedMusim-GapNumber indicates the preferred number of aperiodicmusim-Gap.

If the requested gap is periodic gap, RequestedMusim-GapOffset1 andRequestedMusim-GapLength1 and RequestedMusim-GapRepetitionPeriod1 areincluded.

If the requested gap is aperiodic gap, RequestedMusim-GapOffset2 andRequestedMusim-GapLength2 and RequestedMusim-GapRepetitionPeriod2 andRequestedMusim-GapNumber are included.

RequestedMusim-GapOffset1 is an integer between 0 and 159.RequestedMusim-GapOffset2 is an integer between 0 and 10239.

RequestedMusim-GapLength1 is enumerated with eight values: ms1Dot5, ms3,ms3dot5, ms4, ms5dot5, ms6, ms10, ms20.

RequestedMusim-GapLength2 is enumerated with four values: ms32, ms64,ms128, ms256.

RequestedMusim-GapRepetitionPeriod1 is enumerated with four values:ms20, ms40, ms80, ms160.

RequestedMusim-GapRepetitionPeriod2 is enumerated with four values:ms64, ms128, ms256, ms512.

RequestedMusim-GapRepetitionPeriod1is enumerated with four values: one,two, four, eight.

Type6Gap-Preference IE may include Type6Gap-bitmap IE or may include nosub-level IE.

The Type6Gap-bitmap is 4bit. Each bit corresponds to a specific Type6Gappattern. The first bit corresponds to a first Type6Gap pattern, thesecond bit corresponds to a second Type6Gap pattern and so on. Each ofthe first Type6Gap pattern and the second Type6Gap pattern and the thirdType6Gap pattern is associated with a specific gap length and a specificgap repetition periodicity respectively.

The fourth Type6Gap pattern is associated with two gap lengths. Thefirst gap length is applicable when the SCS of the active UL BWP of afirst cell is 15 KHz or 30 KHz and the second gap length is applicablewhen the SCS of the active UL BWP of a first cell is 60 KHz or 120. Thefirst cell is the SpCell of the UE. The first cell could be the servingcell with the shortest SCS among the configured serving cells in FR2.The first cell could be the serving cell with the longest SCS among theconfigured serving cells in FR2.

UE determines which type6Gap is required based on uplink transmissionpower situation and sets the corresponding bit accordingly.

In 2A-17, UE transmits GNB second RRC message.

If the first RRC message was RRCResume message, the second RRC messageis RRCResumeComplete message. The RRCResumeComplete message can includeeither NeedForGapsInfoNR or NeedForGapsInfoNR and NeedForGapsInfoNR2 orNeedForGapsInfoNR and NeedForGapsInfoNR3.

If the first RRC message was RRCReconfiguration message, and if UEconsider itself to be configured to provide the measurement gaprequirement information, the second RRC message isRRCReconfigurationComplete message. The RRCReconfigurationCompletemessage can include either NeedForGapsInfoNR or NeedForGapsInfoNR andNeedForGapsInfoNR2 or NeedForGapsInfoNR and NeedForGapsInfoNR3.

If the first RRC message was RRCReconfiguration message, and if UEconsider itself to be configured to provide MUSIM assistance informationor configured to provide its preference on type6Gap , the second RRCmessage is UEAssistanceInformation message.

The RRCReconfigurationComplete message includes sametransaction-identifier as the transaction-identifier included inRRCReconfiguration message.

The RRCResumeComplete message includes same transaction-identifier asthe transaction-identifier included in RRCResume message.

UEAssistanceInformation message does not include transaction-identifier.

GNB receives the second message and determines gap configurations forthe UE.

In 2A-19, GNB transmits UE third RRC message to indicate gapconfiguration.

The third message can be RRCReconfiguration message.

To configure Type 1Gap or Type2Gap or Type3Gap or Type4Gap or Type7Gap,GNB includes MeasConfig IE in the RRCReconfiguration message. TheMeasConfig IE specifies measurements to be performed by the UE. TheMeasConfig IE includes measGapConfig IE.

MeasGapConfig IE may include a gapFR2 field and a gapFR1 field and agapUE field and a PosMeasGapPreConfigToAddModList field and aPosMeasGapPreConfigToReleaseList field and a gapToAddModList field and agapToReleaseList field.

GAPFR2 and gapFR1 and gapUE are defined as SetupRelease. If gapFR2(orgapFR1 or gapUE) is set to “setup”, a gapConfig IE is included in thegapFR2(or gapFR1 or gapUE) and a FR2-gap (or FR1-gap or UE-gap) issetup. If gapFR2(or gapFR1 or gapUE) is set to “release”, correspondinggapConfig is released.

GAPToReleaseList consist of one or more MeasGapId IEs. gapToAddModListconsist of one or more GapConfig1 IEs.

PosMeasGapPreConfigToReleaseList consist of one or more MeasGapId2 IEs.PosMeasGapPreConfigToAddModList consist of one or more GapConfig2 IEs.

During per-UE measurement gaps, UE does not conductreception/transmission from/to the NR serving cells across FR1 and FR2except the reception of signals used for RRM measurement(s), PRSmeasurement(s) and the signals used for random access procedure.

During per-FR1 measurement gaps, UE does not conductreception/transmission from/to the FR1 NR serving cells except thereception of signals used for RRM measurement(s), PRS measurement(s) andthe signals used for random access procedure.

During per-FR2 measurement gaps, UE does not conductreception/transmission from/to the FR2 NR serving cells except thereception of signals used for RRM measurement(s), PRS measurement(s) andthe signals used for random access procedure.

GAPFR2 and gapFR1 and gapUE are used to configure a type1Gap.

GAPToAddModList is used to configure one or more Type2Gaps or Type3Gapsor Type4Gaps. PosMeasGapPreConfigToAddModList is used to configure oneor more Type7Gaps.

A gapConfig IE indicates the time pattern of the type1Gap. A gapConfigIE includes a gapOffset and a mgl1 and a mgrp and a mgta and a mgl2.

A gapConfig1 IE indicates the time pattern of the type2/3/4gap. AgapConfig1 IE includes measGapId and gapType and gapOffset and mgl3 andmgrp and mgta andtype2Indicator and type4Indicator.

A gapConfig2 IE indicates the time pattern of the type7gap. A gapConfig2IE includes measGapId2 and gapType and gapOffset and mgl3 and mgrp andmgta.

gapOffset indicates an integer between 0 and 159 (i.e., highest mgrp-1).Mgl1 is enumerated with six values: ms1Dot5 and ms3 and ms3dot5 and ms4and ms5dot5 and ms6. value ms1Dot5 corresponds to 1.5 ms. value 3 mscorresponds to 3 ms and so on.

Mgl2 is enumerated with two values: ms10 and ms20. mgl and mgl2 indicatethe length of gap. If both mgl and mgl2 are included in a gapConfig,mgl2 is applied and mgl is ignored.

Mgl3 is enumerated with eight values: ms1Dot5 and ms3 and ms3dot5 andms4 and ms5dot5 and ms6 and ms10 and ms20.

Mgl3 is union of mgl1 and mgl2.

Mgrp is enumerated with four values: ms20, ms40, ms80 and ms160.

Mgta IE is enumerated with three values: ms0, ms0dot25 and ms0dot5. mgtaIE indicates the measurement gap timing advance (or interruption timingadvance in case of Type4Gap) in ms.

GapType indicates the type of this measurement gap. Value perUEindicates that it is a per UE measurement gap, value perFR1 indicatesthat it is an FR1 measurement gap, and value perFR2 indicates that it isan FR2 measurement gap.

type4Indicator is enumerated with a single value of “True”. If this IEis present in the GapConfig1, The GapConfig1 is the configuration oftype4Gap.

type2Indicator is enumerated with a single value of “True”. If this IEis present in the GapConfig1, The GapConfig1 is the configuration oftype2Gap.

If a GapConfig1 includes neither type4Indicator nor type2Indicator,GapConfig is the configuration of type3Gap.

A measGapId IE is an integer between 1 and 8. A measGapld identifies ameasurement gap configuration of a type2Gap or a type3Gap or a type4Gap.Hence different measGapld is allocated across the types of measurementgaps and frequency regions of measurement gaps (i.e. a per-FR1 type3Gapand a per-FR2 type3Gap shall be allocated with different measGapld).

A measGapId2 IE is an integer between 1 and 16. A measGapId2 identifiesa type7 measurement gap configuration. A measGapId and a measGapId2 areallocated independently (i.e. a measGapId x and a measGapId2 x areassociated with two different measurement gap configurations).

To configure Type5Gap, GNB includes musim-GapConfig IE in theRRCReconfiguration message. musim-GapConfig IE indicates the gapconfiguration of Type5Gap that applies to all frequencies. amusim-GapConfig IE includes a single musim-GapToReleaseList IE and asingle musim-GapToAddModList IE. A musim-GapToReleaseList consists ofone or more musim-GapId. A musim-GapToAddModList consists of one or moremusim-GapToAddMod IEs.

A musim-GapToAddMod IE can include musim-gapId,musim-Starting-SFN-AndSubframe, musim-GapLength andmusim-GapRepetitionAndOffset.

A musim-gapId IE is an integer between 0 and 1.

MUSIM-Starting-SFN-AndSubframe IE indicates the gap starting positionfor the aperiodic type5 gap. It includes starting SFN and startingsubframe.

MUSIM-GapRepetitionAndOffset indicates the gap repetition period in msand gap offset in number of subframes. It includes an integer chosenfrom a integer set. The highest value of the integer set is equal to therepetition period-1. The integer indicates the starting offset of thegap. For example, a integer chosen from a integer set with highest valueof 1279 indicates that the repetition period is 1280 ms. UE determinesthe offset based on the signaled integer and the repetition period basedon the highest integer of the integer set.

If musim-gap is periodic gap, musim-GapLength andmusim-GapRepetitionAndOffset are present.

If musim-gap is aperiodic gap, musim-Starting-SFN-AndSubframe ispresent.

To configure Type6Gap, GNB includes Type6GapConfig IE in theRRCReconfiguration message. Type6GapConfig IE indicates the gapconfiguration of Type6Gap that applies to a specific FR (i.e. FR2).Type6GapConfig IE includes a gapOffset field and a ugl field and a ugrpfield.

Ugl field indicates one of ms0dot125 and ms0dot25 and ms0dot5 and ms 1 .ms0dot125 corresponds to 0.125 ms, ms0dot25 corresponds to 0.25 ms andso on. ugl indicates a length of the type6 gap.

Ugrp field indicates the gap repetition period of the type6 gap. ugrpfield indicates one of ms5 and ms20 and ms40 and ms160.

Type6GapRefServCellIndicator field indicates a serving cell identifierwhose SFN and subframe is used for type6Gap calculation for gap pattern.If this field is absent, UE uses PCell for this purpose.

In 2A-21, UE setup the gap based on the gap information received in2A-17.

If the third message includes measGapConfig IE, UE determines the gap tobe setup according to the gapType .

For each GapConfg1 received in gapToAddModList, UE setup the gapconfiguration indicated by the GapConfig1 in accordance with gapOffset,i.e., the first subframe of each gap occurs at an SFN and subframemeeting the following condition:

-   -   SFN mod T=FLOOR(gapOffset/10);    -   Subframe=gapOffset mod 10;    -   With T=mgrp/10;

UE apply the specified timing advance mgta to the gap occurrencescalculated above (i.e., the UE starts the measurement mgta ms before thegap subframe occurrences).

UE apply the measurement gap as per UE measurement gap, FR1 measurementgap, or FR2 measurement gap according to the gapType indicated by theGapConfig1.

UE associate the measurement gap with the measGapld indicated by theGapConfig1;

For each GapConfg2 received in PosMeasGapPreConfigToAddModList, UE setupthe gap configuration indicated by the GapConfig2 in accordance withgapOffset, i.e., the first subframe of each gap occurs at an SFN andsubframe meeting the following condition:

-   -   SFN mod T=FLOOR(gapOffset/10);    -   subframe=gapOffset mod 10;    -   with T=mgrp/10;

UE apply the specified timing advance mgta to the gap occurrencescalculated above (i.e., the UE starts the measurement mgta ms before thegap subframe occurrences).

UE apply the measurement gap as per UE measurement gap, FR1 measurementgap, or FR2 measurement gap according to the gapType indicated by theGapConfig.

UE associate the measurement gap with the measGapId2 indicated by theGapConfig2;Periodic Type5Gap is established as below.

UE setup the gap configuration indicated by the musim-GapConfig inaccordance with the received musim-GapRepetitionAndOffset-, i.e., thefirst subframe of each gap occurs at an SFN and subframe meeting thefollowing condition:

-   -   SFN mod T=FLOOR(INTEGER1/10);    -   Subframe=gapOffset mod 10;    -   With T=MUSIM-PERIODICITY/10;

INTEGER1 is the integer indicated by musim-GapRepetitionAndOffset.MUSIM-PERIODICITY is equal to the highest value of the correspondinginteger set plus one. The corresponding integer set is the one whereINTEGER1 is chosen.

Aperiodic Type5Gap is established as below.

UE setup the gap configuration indicated by the musim-GapConfig inaccordance with musim-Starting-SFN-AndSubframe, i.e., the first subframeof the aperiodic gap occurs at an SFN and subframe indicated inmusim-Starting-SFN-AndSubframe.

Type6Gap is established as below.

UE setup the gap configuration indicated by the type6GapConfig inaccordance with the received gapOffset, i.e., the first subframe of eachgap occurs at an SFN and subframe meeting the following condition:

-   -   SFN mod T=FLOOR(gapOffset/10);    -   Subframe=gapOffset mod 10 if ugrp is larger than 5 ms;    -   Subframe=gapOffset or gapOffset+5 ifugrp is equal to 5 ms;    -   With T=CEIL(ugrp/10);

Each gap occurs (or begins) at the first static uplink slot determinedfrom the first subframe (i.e., each gap occurs/begins at the firststatic uplink slot starting from the first slot of the first subframe).

For each FR1, FR2, and per UE measurement gap that is setup, if themeasurement gap is configured by GapConfig 1 and type2Indicator in thecorresponding GapConfig 1 is present, UE determine whether themeasurement gap is activated or not based on the activated BWP and/oractivated SCells.

For each FR1, FR2, and per UE measurement gap that is setup, if themeasurement gap is configured by GapConfig2, UE consider the measurementgap is deactivated.

For each FR1, FR2, and per UE measurement gap that is setup, if themeasurement gap is configured by GapConfig1 and type2Indicator in thecorresponding GapConfig1 is not present or if the measurement gap isconfigured by GapConfig, UE consider the measurement gap is activated.

For each type5Gap that is setup, UE consider the gap is activated.

For each type6Gap that is setup, UE consider the gap is activated.

In short, type 1Gap and type3Gap and type4Gap and type5Gap and type6Gapare considered activated when they are configured by a RRC message.Type2Gap is either activated or deactivated depending on the active BWPand/or active SCel when it is configured by a RRC message. Type7Gap isconsidered deactivated when it is configured by a RRC message.

All the Type1Gap and Type3Gap and Type4Gap and Type5Gap are immediatelyused (i.e., used from the next occurrence) once the corresponding gapconfigurations are setup.

One or more Type2Gap configurations can be setup. However only subset ofType2Gaps is used depending on the currently active downlink BWP.

One or more Type7Gap configurations can be setup. However only one ofType7Gaps is used when DL MAC CE activate the Type7Gap.

Only one Type1Gap or only one Type4Gap can be configured and used asFR1-gap. one or two Type3Gap can be configured and used simultaneouslyas FR1-gap.

Only one TypelGap or only one Type4Gap can be configured as FR2-gap. oneor two Type3Gap can be configured and used simultaneously as FR2-gap.

Only one TypelGap or only one Type4Gap can be configured and usedsimultaneously as UE-gap. One or more Type2Gap can be configured asUE-gap. One or more Type5Gap can be configured as UE-gap. Only oneType2Gap can be used as UE-gap. One or more Type5Gap can be used asUE-gap simultaneously.

A certain IE (or field) being enumerated with x and y means that theIE(or field) can indicate one of x and y.

In 2A-23, UE applies gap operations during a gap. UE performs normaloperations during non-gap.

TABLE 5 Gap type Applied gap operation Type1Gap Gap Operation 1 duringthe gap Type2Gap Gap Operation 1-1 during the gap Type3Gap Gap Operation1-1 during the gap Type4Gap Gap Operation 2 during interruption lengthGap operation 3 during measurement length Type5Gap Gap Operation 4during the gap Type6Gap Gap Operation 6 during the gap Type7Gap GapOperation 1-2 during the gap

A gap being active means the relevant gap operation being applied. A gapbeing inactive means the relevant gap operation not being applied andnormal operation being applied as if gap is not configured.

Gap operation comprises data-activity-action-group andnon-data-activity-action-group.

TABLE 6 Gap operation non-data- type data-activity-action-groupactivity-action-group Gap For serving-carrier-group, performing SSBbased operation 1 not performing the measurement on transmission of HARQmeasurement-object- feedback, SR, and CSI in the group. uplink slots andin the uplink symbols of flexible slots during the gap. not reportingSRS in the uplink slots and in the uplink symbols of flexible slotsduring the gap. not transmitting on UL-SCH except for Msg3 or the MSGApayload in the uplink slots and in the uplink symbols of flexible slotsduring the gap. not monitoring the PDCCH in the downlink slots and inthe downlink symbols of flexible slots during the gap except period X.not receiving on DL-SCH in the downlink slots and in the downlinksymbols of flexible slots during the gap except period X. period X iswhen ra- ResponseWindow or the ra- ContentionResolutionTimer or themsgB-Response Window is running Gap same data-activity-action-performing SSB based operation group as Gap operation 1 measurement orCSI- 1-1 RS based measurement or PRS based measurement onmeasurement-object- group. Gap same data-activity-action- performing PRSbased operation group as Gap operation 1 measurement on a 1-2 group offrequencies. The frequencies where PRS measurement is performed areindicated by LMF in a LPP message or indicated by GNB in a systeminformation. Gap same data-activity-action- RF retuning operation 2group as Gap operation 1 Gap For serving-carrier-group, same non-data-operation 3 performing the activity-action-group transmission of HARQ asGap operation 1-1 feedback, SR, and CSI in the uplink slots and in theuplink symbols of flexible slots during the gap. reporting SRS in theuplink slots and in the uplink symbols of flexible slots during the gap.transmitting on UL-SCH in the uplink slot sand in the uplink symbols offlexible slots during the gap monitoring the PDCCH in the downlink slotsand in the downlink symbols of flexible slots during the gap. receivingon DL-SCH in the downlink slots and in the downlink symbols of flexibleslots during the gap. Gap same data-activity-action- performing pagingoperation 4 group as Gap operation 1 reception or system informationreception for the other USIM Gap For serving-carrier- operation 6 group(i.e. FR2 serving cells), not performing the transmission of HARQfeedback and CSI during the gap. not reporting SRS during the gap. nottransmitting on UL-SCH except for Msg3 or the MSGA payload and exceptfor CG-PUSCH during the gap. performing transmission on PUCCH allocationfor SR and on CG-PUSCH resource and PRACH resource

Type 1 gap and type 2 gap and type 3 gap and type 4 gap and type 5 gapand type7 gap consist with all types of slots (i.e. uplink slots anddownlink slots and flexible slots indicated intdd-UL-DL-ConfigurationCommon). A type 1 gap or a type 2 gap or a type 3gap or a type 4 gap or a type 5 gap are consecutive in time within therespective gap (i.e. if the gap length is n ms, the distance between thestarting point of the gap and the end point of gap is n ms) and consistwith consecutive slots.

Type 6 gap consists with only static UL slots indicated intdd-UL-DL-ConfigurationCommon. Type 6 gap could be non-consecutive intime (i.e. if the gap length is n ms, the distance between the startingpoint of the gap and the end point of gap could be longer than n ms) andconsists with slots that could be non-consecutive with each other.

Time span of a gap is between the starting point of the gap and the endpoint of the gap.

During the time span of a type X gap (X is 1 or 2 or 3 or 4), UE is notrequired to (i.e. UE does not) conduct reception/transmission from/tothe corresponding NR serving cells in the corresponding frequency rangeexcept the reception of signals used for RRM measurement(s) and thesignals used for random access procedure.

During the time span of type 6 gap, UE is not required to(i.e. UE doesnot) conduct transmission to the corresponding NR serving cells in FR2except for the signals used for random access procedure, CG-PUSCH (type1 and 2) and PUCCH allocations for SR and LRR. During the time span oftype 6 gap, UE conduct reception from the corresponding NR serving cellin FR2.

serving-carrier-group and measurement-object-group are determined as intable.

TABLE 7 Gap Type serving-carrier-group measurement-object-group Type1GapIf the gap is FR2 gap, If the gap is FR2 gap, serving-carrier-group ismeasurement-object-group is the serving carriers (or measurement objectsconfigured serving cells) on FR2. for FR2 frequencies. If the gap is FR1gap, If the gap is FR1 gap, serving-carrier-group ismeasurement-object-group is the serving carriers (or measurement objectsconfigured serving cells) on FR1. for FR1 frequencies. If the gap is UEgap, If the gap is UE gap, serving-carrier-group ismeasurement-object-group is the all serving carriers (or measurementobjects configured serving cells) or serving for FR1 frequencies and FR2carriers (or serving frequencies. cells) on FR1 and FR2. Type2Gap Sameas Type1Gap Same as Type1Gap Type3Gap Same as Type1Gap Regardless ofwhether the gap is FR1 gap or FR2 gap or UE gap, measurement-object-group is determined based on the associated measurement objects. If thegap is FR2 gap, only the measurement objects on FR2 can be associatedwith the gap. If the gap is FR1 gap, only the measurement objects on FR1can be associated with the gap. Type4Gap Same as Type1Gap Same as Type1Gap Type5Gap Type5Gap is UE gap. Type5Gap is UE gap.serving-carrier-group is measurement-object- all serving carriers (orgroup is the measurement objects serving cells) or serving configuredfor FR1 frequencies carriers (or serving cells) and FR2 frequencies. onFR1 and FR2. Type6Gap Type6Gap is FR2 gap N/A (UE is not required toperform measurement) Type7Gap Same as Type1Gap Measurement-object- groupis a group of frequencies where PRS is configured.

In 2A-25, GNB performs transmission and reception with the UEconsidering the activated gaps.

Type2Gap is described in more detail below.

A Type2Gap is associated with a DL BWP according to type2GapStatus 1 forthe DL BWP. A BWP-DownlinkDedicated IE can include a type2GapStatus1 IE.

The type2GapStatus1 is a bit string. type2GapStatus1 indicates whetherthe type2 gaps are activated or deactivated upon the switch to this BWP.The first/leftmost bit corresponds to the measurement gap with gap ID 1,the second bit corresponds to measurement gap with gap ID 2, and so on.Value 0 indicates that the corresponding type2 gap is deactivated whilevalue 1 indicates that the corresponding type2 gap is activated. The UEshall ignore the bit if the corresponding measurement gap is not a type2gap.

A SCellConfig IE can include a type2GapStatus2 IE.

type2GapStatus2 is a bit string. Type2GapStatus2 indicates whether thetype2 gaps are activated or deactivated while this SCell is deactivated.The first/leftmost bit corresponds to the measurement gap with gap ID 1,the second bit corresponds to measurement gap with gap ID 2, and so on.Value 0 indicates that the corresponding type2 gap is deactivated whilevalue 1 indicates that the corresponding type2 gap is activated. The UEshall ignore the bit if the corresponding measurement gap is not a type2gap.

One or more Type2gaps can be configured for a UE. Among the gaps, UEactivates a specific gap. The specific gap is the gap determined fromthe type2GapStatus1 of the active DL BWP or the gap determined from thetype2GapStatus2 of the active SCell.

Type2Gap switching occurs when BWP switching occurs. More specifically,BWP switching occurs in the following cases.

Upon configuring Type2Gaps and DL BWPs based on a receivedRRCReconfiguration message, UE activates a Type2Gap determined from thetype2GapStatus 1 of a DL BWP to be activated after RRC reconfiguration.If firstActiveDownlinkBWP is present in the RRCReconfiguration message,the DL BWP to be activated is the DL BWP indicated byfirstActiveDownlinkBWP-Id in the RRCReconfiguration message. IffirstActiveDownlinkBWP-Id is absent in the RRCReconfiguration message,the DL BWP to be activated in the DL BWP that was active beforeRRCReconfiguration message is received.

After activating a Type2Gap, UE may need to do gap switching (i.e., UEmay need to deactivate the current active Type2Gap and to activate a newType2Gap). For example, if UE receives uplink grant on PDCCH (DCI format0_1 or 0_2) including a bandwidthpart indicator field indicating an ULBWP different from the current active UL BWP, UE determines that gapswitching is needed if condition 1 and condition 2 are fulfilled.

Condition 1: If the SpCell of the UE is in unpaired spectrum (i.e., TDDspectrum); and

Condition 2: If the active Type2Gap associated with the old DL BWP (DLBWP that is active before reception of the UL grant on PDCCH) isdifferent from the Type2Gap to be activated upon switch to the DL BWPhaving the same BWP id as the UL BWP indicated by the bandwidthpartindicator of the UL grant.

If both conditions are fulfilled, UE deactivates the current Type2Gapand activates the Type2Gap associated with the DL BWP having the sameBWP id as the UL BWP indicated by the bandwidthpart indicator of the ULgrant. If no Type2Gap is associated with the DL BWP, no Type2Gap isactivated.

If UE receives DL assignment on PDCCH (DCI format 1_1 or 1_2), UEdetermines gap switching is needed if condition 3 is fulfilled.

Condition 3: If the active Type2Gap associated with the old DL BWP isdifferent from the Type2Gap to be activated upon switch to the DL BWPindicated by the bandwidthpart indicator of the DL assignment

If condition 3 is fulfilled, UE deactivates the current Type2Gap andactivates the Type2Gap determined from the type2GapStatus1 of the DL BWPindicated by the bandwidthpart indicator of the DL assignment. Iftype2GapStatus1 is not configured to the DL BWP, all the configuredType2Gaps are activated.

If the bwp-InactivityTimer associated with the active DL BWP expires, UEdetermines gap switching is needed if condition 4 is fulfilled.

condition 4: If the active Type2Gap associated with the active DL BWP(old DL BWP) is different from the Type2Gap to be activated upon switchto the DL BWP to be activated

If defaultDownlinkBWP-Id is configured, The DL BWP to be activated isthe DL BWP indicated by the defaultDownlinkBWP-Id.

If defaultDownlinkBWP-Id is not configured, The DL BWP to be activatedis the DL BWP indicated by the initialDownlinkBWP.

If condition 4 is fulfilled, UE deactivates the current Type2Gap andactivates the Type2Gap determined from the type2GapStatus1 of the DL BWPto be activated.

If Random Access procedure is initiated on a serving cell, UE determinesgap switching is needed if condition 5 and condition 6 are fulfilled.

Condition 5: If PRACH occasions are not configured for the active UL BWPand if the serving cell is SpCell

Condition 6: If the active Type2Gap associated with the active DL BWP(old DL BWP) is different from the Type2Gap to be activated upon switchto the DL BWP indicated by initialDownlinkBWP.

If condition 5 and 6 are fulfilled, UE deactivates the current Type2Gapand activates the Type2Gap associated with the DL BWP indicated byinitialDownlinkBWP. If no Type2Gap is associated with the initial DLBWP, no Type2Gap is activated.

Alternatively, a BWP-DownlinkDedicated IE and a SCellConfig IE caninclude a deactivatedMeasGapBitmap IE respectively.

Each bit of The deactivatedMeasGapBitmap indicates the Type2GapStatus ofeach type2Gap.

One UE-Type2gap or one FR1-Type2gap or one FR2-Type2gap or oneFR1-Type2gap and one FR2-Type2gap can be configured for the UE.

If Type2GapStatus of the active DL BWP of the PCell is set to a firstvalue (e.g., deactivated), UE deactivates the Type2Gap for the PCell.

If Type2GapStatus of the active DL BWP of the PCell is set to a secondvalue (e.g., activated), UE activates the Type2Gap for the PCell.

The other way is also possible.

If Type2GapStatus of the active DL BWP of the PCell is set to a firstvalue (e.g., activated), UE activates the Type2Gap for the PCell.

If Type2GapStatus of the active DL BWP of the PCell is set to a secondvalue (e.g., deactivated), UE deactivates the Type2Gap for the PCell.

The initial DL BWP is the BWP of which BWP-id is 0. The initial DL BWPis the BWP of which BWP-id is implicitly configured. The initial BWP isthe BWP of which BWP-id is not associated with an explicit BWP-Id IE.The initial DL BWP is the BWP of which cell specific configuration isprovided in SIB1 and UE specific configuration is provided inRRCReconfiguration message. DL BWPs other than the initial BWP are theBWP of which cell specific configuration and UE specific configurationare provided in RRCReconfiguration message.

Type2Gap switching occurs when SCell activation/deactivation occurs.

Upon configuring Type2Gaps and a SCell based on a receivedRRCReconfiguration message, UE activates a Type2Gap determined from thetype2GapStatus2 of the SCell.

Upon reception of a first MAC CE activating or deactivating the SCell,UE activates a Type2Gap determined from the type2GapStatus2 of theSCell.

Upon expiry of sCellDeactivationTimer configured for the SCell, UEactivates a Type2Gap determined from the type2GapStatus2 of the SCell.

Alternatively, upon configuring Type2Gaps and a SCell based on areceived RRCReconfiguration message, UE deactivates one or two Type2Gapdetermined from the type2GapStatus2 of the SCell.

Upon reception of a MAC CE activating or deactivating the SCell, UEdeactivates one or two Type2Gap determined from the type2GapStatus2 ofthe SCell.

Upon expiry of sCellDeactivationTimer configured for the SCell, UEdeactivates one or two Type2Gap determined from the type2GapStatus2 ofthe SCell.

Type2Gap switching occurs when a second MAC CE activating a Type2Gap isreceived.

Upon receiving the second MAC CE, UE activates the type2Gap indicated inthe second MAC CE.

When BWP switch occurs, which results in status change of Type2Gap (i.e.Type2Gap activation or deactivation or both), UE finishes type2Gapactivation or deactivation within 5+x ms since BWP switch occur (i.e.since DCI reception or timer expiry). x is determined based at leastpart on bwp-SwitchingDelay and SCS of the BWPs as in table below.

TABLE 8 shorter SCS between old BWP and slot Type Type the new BWPlength 1 2  15 kHz    1 ms   1 ms   3 ms  30 kHz  0.5 ms   1 ms  2.5 ms 60 kHz  0.25 ms 0.75 ms 2.25 ms 120 kHz 0.125 ms 0.75 ms 2.25 ms

BWP-SwitchingDelay defines whether the UE supports DCI and timer basedactive BWP switching delay type1 or type2. It indicates one of type1 andtype2.

When SCell is deactivated due to the first MAC CE reception, UE finishestype2Gap activation or deactivation within 5+y ms since the first MAC CEdeactivating the SCell is received. y is determined based at least parton the timing when acknowledgement for the first MAC CE is transmitted.y is equal to 3+y1 ms, where y1 is the timing between the first MAC CEtransmission and the corresponding acknowledgement.

When SCell is deactivated due to the expiry of sCellDeactivationTimer,UE finishes type2Gap activation or deactivation within 5+y2 ms since theexpiry of sCellDeactivationTimer. y2 is fixed to 3.

When SCell is activated or deactivated due to reception ofRRCReconfiguration message, UE finishes type2Gap activation ordeactivation within 5+z ms since the RRCReconfiguration message isreceived. z is 10 ms if RRCReconfiguration includes the configuration onPCell and does not includes the configuration on SCell addition/release.z is 16 ms if RRCReconfiguration includes the configuration on SCelladdition/release.

The first MAC CE is SCell Activation/Deactivation MAC CE. The second MACCE is Type2Gap L2 response MAC CE.

Type6Gap is described in more detail below.

The length of the type6Gap in terms of the number of slots is determinedbased on ugl field and type6GapRefServCellIndicator field. UE firstdetermines the number of uplink slots from the gap length indicated bythe ugl field and the SCS of the serving cell indicated bytype6GapRefServCellIndicator. For example, if the gap length is 0.5 msand UL SCS of the reference serving cell is 60 KHz, the number of slotsfor a type6Gap is 2 (=gap length/slot length of the reference servingcell). If type6GapRefServCellIndicator field is absent intype6GapConfig, UE determines the number of uplink slots based on uglfield and the SCS of the active UL BWP of the PCell.

Type6Gap starts in the nearest uplink slot from the referencesubframe(or the first subframe). Type6Gap continues for consecutive nuplink slots. Depending on tdd-UL-DL-ConfigurationCommon, DL slots andflexible slots can exists between uplink slots(or within time span ofuplink slots). Hence the actual length of type6Gap is determined by thenumber of uplink slots derived from type6GapLength field and the numberof downlink slots that exist within the time span of the uplink slotsand the number of flexible slots that exist within the time span of theuplink slots. UE performs normal downlink operation in the downlinkslots and flexible slots within the Type6Gap. UE performs normal uplinkoperation in the flexible slots within the Type6Gap. UE stops any uplinkoperation in the uplink slots within the Type6Gap. UE does not performuplink transmission of FR1 serving cells in the uplink slots during FR1type6Gap. UE does not perform uplink transmission of FR2 serving cellsin the uplink slots during FR2 type6Gap. UE does not perform uplinktransmission of all serving cells in the uplink slots during UEtype6Gap.

If Type7Gap needs to be updated or to be activated with regards tolocation measurement, UE moves to step 2A-27.

In 2A-27, UE transmits and GNB receives a type7Gap activation requestmessage. The message could be either type7Gap L3 request message(type7Gap activation request RRC message) or type7Gap L2 request message(type7Gap activation request MAC CE).

If performing location measurements towards NR is started and the UErequires measurement gaps for these operations while measurement gapsare either not configured or not sufficient, and if type7Gaps areconfigured and the UE considers that at least one of type7Gap issufficient for the location measurement when activated, UE initiatestype7 gap activation request using UL MAC CE. The UL MAC CE is Type7GapL2 request message.

If performing location measurements towards NR is started and the UErequires measurement gaps for these operations while measurement gapsare either not configured or not sufficient, and if type7Gaps are notconfigured, UE initiates the type7 gap activation request using UL RRCmessage that includes a measruementIndication field set tonr-PRS-Measurement.

If performing location measurements towards NR is started and the UErequires measurement gaps for these operations while measurement gapsare either not configured or not sufficient, and if type7Gaps areconfigured and the UE considers that none of type7Gap is sufficient forthe location measurement when activated, UE initiates the type7 gapactivation request using UL RRC message that includes ameasruementIndication field set to nr-PRS-Measurement.

If location measurements towards NR is stopped and if there is anactivated type7gap, UE initiates type7 gap deactivation request using ULMAC CE.

If location measurements towards NR is stopped and if there is noactivated type7gap, UE triggers type7Gap L3 request procedure toinitiate transmission of the type7Gap L3 request message that includes ameasurementIndication field set to release.

If at least one type7Gap L2 request is triggered, UE cancel the alreadytriggered type7Gap L2 request message, if any, and triggers new type7GapL2 request message.

If Type7Gap L2 request message has been triggered, and not cancelled andif UL-SCH resources are available for a new transmission and theseUL-SCH resources can accommodate the Type7Gap L2 request message plusits subheader as a result of logical channel prioritization, UE canceltriggered Type7Gap L2 request message and generates the Type7Gap L2request message.

If Type7Gap L2 request message has been triggered, and not cancelled andif UL-SCH resources are not available for a new transmission, UEtriggers a Scheduling Request for Type7Gap L2 request message withouttriggering BSR.

UE applies a first SR configuration to the scheduling request proceduretriggered for Type7Gap L2 request message.

UE is configured with one or more SR configurations. The first SRconfiguration is selected from the one or more SR configurationsimplicitly or explicitly.UE performsscheduling_request_procedure_for_Type7Gap_L2_request.

In 2A-29, GNB transmits and UE receives a type7Gap activation responsemessage. The message could be either type7Gap L3 response message(type7Gap activation response RRC message) or type7Gap L2 responsemessage (type7Gap activation response MAC CE). If UE transmittedtype7Gap L2 request message, GNB respond with type7Gap L2 responsemessage. If UE transmitted type7Gap L3 request message, GNB respond withtype7Gap L3 response message.

Upon the reception of the Type7Gap L2 response message, if the messageindicates deactivation of a type7Gap UE deactivates the type7Gap and ifthe message indicates activation of a type7Gap UE activates thetype7Gap.

In 2A-31, UE and GNB performs RRC_CONNECTED operation (e.g. datatransmission/reception) according to the configured and activated gap.

During the RRC_CONNECTED operation, UE may detect some events andinitiates RRC re-establishment procedure. The event includes detectingradio link failure, re-configuration with sync failure, integrity checkfailure and RRC connection reconfiguration failure.

Upon such failures, UE needs to re-establish the RRC connection in thenew cell. To perform this task quickly, UE stops all other tasks likegap request or preference indication. Also, since gap operationrestricts the UE activity, UE stops gap operation as well.

In 2A-33, UE performs RRC re-establishment procedure.

Upon initiation of RRC re-establishment procedure and beforetransmission RRCReestablishmentRequest in the selected suitable cell, UEreleases configuration information for gap request such asneedForGapsConfigNR, needForGapsConfigNR2, needForGapsConfigNR3,musim-AssistanceConfig and needFortype6Gap. UE also cancels anytriggered type2Gap L2 request procedure and discard any type2Gap L2request message.

UE performs cell selection to find a new suitable cell.

Upon selecting a suitable cell, UE applies default MAC Cell Groupconfiguration and CCCH configuration and initiates transmission ofRRCReestablishmentRequest message.

The RRCReestablishmentRequest message includes a ue-Identity field and ashortMAC-I field and a reestablishmentCause field.

UE re-establish PDCP and RLC of SRB1 and transmitsRRCReestablishmentRequest via SRB0.

GNB receives the RRCReestablishmentRequest message and determineswhether to reestablish the RRC connection based on the ue-Identity fieldand the shortMAC-I field and the reestablishmentCause field.

If GNB determines to reestablish RRC connection with the UE, GNBtransmits RRCReestablishment message via SRB1.

UE receives the RRCReestablishment message via SRB1 and release the typex (x is 1 or 2 or 3 or 4 or 7) gap configurations indicated bymeasGapConfig and the type 5 gap configuration indicated bymusim-GapConfig and type 6 gap configuration indicated bytype6GapConfig.

UE transmits to GNB RRCReestablishmentComplete message to confirm thatUE completes the procedure.

In short, UE releases gap request configuration at first point of timeand UE release gap configuration at second point of time. UE can stopgap operation before releasing the configuration to facilitate quickerreestablishment. For example, UE can stop gap operation at first pointof time or at third point of time.

The first point of time is after initiating RRC re-establishmentprocedure and before selecting a suitable cell (or before transmittingRRCReestablishmentRequest message via SRB0).

The second point of time is after receiving RRCReestablishment messagevia SRB1 and before transmitting RRCReestablishmentComplete message viaSRB1.

The third point of time is after transmitting RRCReestablishmentRequestmessage via SRB0 and before receiving RRCReestablishment message viaSRB1.

In the disclosure, ‘mapped’ and ‘associated’ and ‘be related’ are usedinterchangeably.

CellGroupConfig is used to configure a master cell group (MCG) orsecondary cell group (SCG). A cell group comprises of one MAC entity, aset of logical channels with associated RLC entities and of a primarycell (SpCell) and one or more secondary cells (SCells). CellGroupConfigincludes following fields: zero or one spCellConfig, zero or one or moreSCellConfig.

SpCellConfig is parameters for the SpCell of this cell group (PCell ofMCG or PSCell of SCG).

SpCellConfig includes following fields: a servCellIndex, areconfigurationWithSync and a ServingCellConfig

SCellConfig is parameters for the SCell. SCellConfig includes followingfields: a sCellIndex, a ServingCellConfigCommon and a ServingCellConfig.

The SCellIndex is a short identity to identify an SCell.

The reconfigurationWithSync is parameters for the SpCell. IfspCellConfig in CellGroupConfig in RRCReconfiguration includesreconfigurationWithSync, handover is initiated. ThereconfigurationWithSync includes following fields: aServingCellConfigCommon, a newUE-Identity, t304 and arach-ConfigDedicated.

NewUE-Identity indicates the C-RNTI to be used in the target cell afterhandover.

ServingCellConfigCommon includes one DownlinkConfigCommon and twoUplinkConfigCommon. One UplinkConfigCommon is for a NUL (normal uplink)and the other UplinkConfigCommon is for a SUL (supplementary uplink).UplinkConfigCommon for a SUL is located after UplinkConfigCommon is fora NUL.

DownlinkConfigCommon includes FrequencyInfoDL and BWP-DownlinkCommon.BWP-DownlinkCommon is for the initial DL BWP and includesPDCCH-ConfigCommon and PDSCH-ConfigCommon.

UplinkConfigCommon includes FrequencyInfoUL and TimeAlignmentTimer andBWP-UplinkCommon. BWP-UplinkCommon is for the initial UL BWP.BWP-UplinkCommon includes RACH-ConfigCommon and PUSCH-ConfigCommon andPUCCH-ConfigCommon and a plurality of RACH-ConfigCommon-fc.

DownlinkConfigCommon is a common downlink configuration of the servingcell. It consists of subfields such as FrequencyInfoDL andBWP-DownlinkCommon.

FrequencyInfoDL is a basic parameter of a downlink carrier. It consistsof subfields such as a frequency band list and carrier bandwidth foreach SCS.

BWP-DownlinkCommon is the configuration of the second downlink IBWP. Itconsists of subfields such as BWP, PDCCH-ConfigCommon, andPDSCH-ConfigCommon. The first IBWP has a frequency domain correspondingto the first CORESET #0 of the MIB and has subcarrier spacing indicatedby the MIB. The first IBWP is the IBWP indicated by the MIB andreceiving 1, the second IBWP is the IBWP indicated by the 1 andreceiving the 2, paging, random access response message, and the like.

BWP is IE that configures general parameters of BWP. It consists ofsubfields such as locationAndBandwidth indicating the bandwidth andlocation of the BWP, and subcarrierSpacing indicating the SCS of theBWP.

ServingCellConfig includes a BWP-DownlinkDedicated (for the secondinitial downlink BWP) and zero or one or more BWP-Downlink IEs (fordedicate downlink BWPs) and a UplinkConfig IE (for normal uplink) and aUplinkConfig IE (for supplementary uplink). The UplinkConfig IE includesa BWP-UplinkDedicated (for the second initial uplink BWP) and zero orone or more BWP-Uplink IEs (for dedicate uplink BWPs).

A BWP-Downlink consists of a BWP-Id IE and a BWP-DownlinkCommon IE and aBWP-DownlinkDedicated IE.

A BWP-Uplink consists of a BWP-Id IE and a BWP-UplinkCommon IE and aBWP-UplinkDedicated IE.

A BWP-DownlinkDedicated consists of a PDCCH-Config and a PDSCH-Config.The PDCCH-Config is used to configure UE specific PDCCH parameters suchas control resource sets (CORESET), search spaces and additionalparameters for acquiring the PDCCH. The PDSCH-Config is used toconfigure the UE specific PDSCH parameters.

A BWP-UplinkDedicated consists of a PUCCH-Config and a PUSCH-Config. ThePUCCH-Config is used to configure UE specific PUCCH parameters. ThePUSCH-Config is used to configure the UE specific PUSCH parameters.

PDCCH-ConfigCommon is the cell-specific PDCCH parameters of the initialBWP of the second cell. It consists of subfields such ascontrolResourceSetZero, commonControlResourceSet, searchSpaceZero,commonSearchSpaceList, searchSpaceOtherSystemInformation,pagingSearchSpace, and ra-SearchSpace.

ControlResourceSetZero is defined as an integer between 0 and 15. Itindicates one of the predefined CORESET #0 configurations. ThecontrolResourceSetZero included in the MIB corresponds to the firstCORESET #0, and the controlResourceSetZero included in thePDCCH-ConfigCommon of the servingCellConfigCommon of SIB1 corresponds tothe second CORESET #0.

SearchSpaceZero is defined as an integer between 0 and 15. It indicatesone of the predefined SS #0 configurations. The searchSpaceZero includedin the MIB corresponds to the first SS #0, and thecontrolResourceSetZero included in the PDCCH-ConfigCommon of theservingCellConfigCommon of SIB1 corresponds to the second S S #0.

CommonControlRe sourceS et is a common CORESET defined byControlResourceSet IE. It defines an additional CORESET that can be usedfor paging reception, random access response reception, systeminformation reception, etc. p CommonSearchSpaceList is a list of commonSSs. The common SS may be used for paging reception, random accessresponse reception, system information reception, and the like.

SearchSpaceOtherSystemInformation is defined by the SS identifier IE. Ifit is 0, the second SS #0 is indicated, and if it is a value other than0, one of the SSs defined in commonSearchSpaceList is indicated.

PagingSearchSpace is defined by the SS identifier IE. If it is 0, thesecond SS #0 is indicated, and if it is a value other than 0, one of theSSs defined in commonSearchSpaceList is indicated.

RA-SearchSpace is defined by the SS identifier IE. If it is 0, thesecond SS #0 is indicated. If it is a value other than 0, one of the SSsdefined in the commonSearchSpaceList is indicated.

PDCCH-ConfigCommon configures one or more TYPE 1 CSSs (Common SearchSpace) and a TYPE2 CSS.

TYPE1 CSS is applicable to and used by both RRC_INACTIVE UE and RRC_IDLEUE. The configuration of TYPE1 CSS is predefined (if it issearchSpaceZero) or referred by one of commonSearchSpaceList.searchSpaceZero and searchSpaceOtherSystemInformation andpagingSearchSpace and ra-SearchSpace are TYPE1 CSS.CommonSearchSpaceList includes one or more SearchSpace IE.

TYPE2 CSS is applicable to and used by only RRC_INACTIVE UE. The type2CSS is configured by a SearchSpace2 IE.

SDT-SearchSpace is TYPE2 CSS.

PDCCH-Config is used to configure UE specific PDCCH parameters such ascontrol resource sets (CORESET), search spaces and additional parametersfor acquiring the PDCCH.

It consists of fields such as controlResourceSetToAddModList,searchSpacesToAddModList and tpc-SRS.

ControlResourceSetToAddModList field includes a list of UE specificallyconfigured Control Resource Sets (CORESETs) to be used by UE.

SearchSpacesToAddModList field includes a list of UE specificallyconfigured Search Spaces.

TPC-SRS field enables and configures reception of group TPC commands forSRS. tpc-SRS field includes SRS-TPC-CommandConfig IE.SRS-TPC-CommandConfig is used to configure UE for extracting TPCcommands for SRS from a group-TPC messages on DCI.

SearchSpace IE defines how/where to search for PDCCH candidates TheSearchSpace IE includes following fields: a searchSpaceId, acontrolResourceSetId, monitoringSlotPeriodicityAndOffset, a duration,searchSpaceType etc.

ControlResourceSetId indicates the CORESET applicable for thisSearchSpace. monitoringSlotPeriodicityAndOffset indicats slots for PDCCHMonitoring configured as periodicity and offset. duration indicatesnumber of consecutive slots that a SearchSpace lasts in every occasion.searchSpaceType indicates whether this is a common search space or a UEspecific search space as well as DCI formats to monitor for.

SearchSpaceId is used to identify Search Spaces. It is an integerbetween 0 and 39.

PDSCH-ConfigCommon is cell-specific PDSCH parameters of the initial BWPof the second cell. It consists of a pdsch-TimeDomainAllocationList. Thepdsch-TimeDomainAllocationList is a list composed of a plurality ofpdsch-TimeDomainAllocations.

PDSCH-TimeDomainAllocation is a time domain relationship between thePDCCH and the PDSCH. It consists of subfields such as K0 andstartSymbolAndLength. K0 is the slot offset between the DCI and thescheduled PDSCH. startSymbolAndLength is an index indicating a validstart symbol and length combination.

PCCH-Config is configuration related to paging. It consists ofsub-fields such as the base station paging period, PF-relatedparameters, and PO-related parameters.

BCCH-config is a configuration related to system information. Itconsists of subfields such as modificationPeriodCoeff indicating thelength of the modification period.

UplinkConfigCommonSlB is a common uplink configuration of the servingcell. It consists of subfields such as frequencyInfoUL,initialUplinkBWP, and timeAlignmentTimerCommon.

FrequencyInfoUL-SIB is a basic parameter of the uplink carrier. Itconsists of subfields such as a frequency band list and carrierbandwidth for each SCS.

BWP-UplinkCommon is the configuration of the second uplink IBWP. Itconsists of subfields such as BWP, rach-ConfigCommon,pusch-ConfigCommon, and pucch-ConfigCommon.

PDSCH-Config IE is used to configure UE specific PDSCH parameters. Itconsists of dataScramblingIdentityPDSCH field andpdsch-TimeDomainAllocationList field and mcs-Table field and others.

DataScramblingIdentityPDSCH field indicates identifier used toinitialize data scrambling (c_init) for PDSCH

MCS-Table field indicates which MCS table UE shall use for PDSCH. If thefield is absent UE applies the value 64QAM. value 64QAM means the MCStable for 64QAM. value 256QAM means the MCS table for 256QAM.

RACH-ConfigCommon is the cell-specific random access parameter of theinitial BWP of the second cell. It consists of subfields such asprach-ConfigurationIndex, msg1-FrequencyStart,preambleReceivedTargetPower, ra-ResponseWindow, preambleTransMax,msg1-SubcarrierSpacing, rsrp-ThresholdSSB , rsrp-ThresholdSSB-SUL,featueCombination and ra-ContentionResolutionTimer.

PUSCH-ConfigCommon is cell-specific PUSCH parameters of the initial BWPof the second cell. It consists of subfields likepusch-TimeDomainAllocationList. The pusch-TimeDomainAllocationList is alist composed of a plurality of pusch-TimeDomainAllocations.

PUSCH-Pusch-TimeDomainAllocation is a time domain relationship betweenthe PDCCH and the PUSCH. It consists of subfields such as K2 andstartSymbolAndLength. K2 is the slot offset between the DCI and thescheduled PUSCH. startSymbolAndLength is an index indicating a validcombination of start symbol and length.

The IE PUSCH-Config is used to configure UE specific PUSCH parametersapplicable to a the initial BWP of the second cell.

It consists of dataScramblingIdentityPUSCH field, pusch-PowerControlfield, pusch-TimeDomainAllocationList field, mcs-Table field andfrequencyHopping field and others.

DataScramblingIdentityPUSCH field indicates an identifier used toinitalize data scrambling (c_init) for PUSCH. If the field is absent, UEapplies the physical cell ID.

MCS-Table field indicates which MCS table UE shall use for PUSCH. If thefield is absent UE applies the value 64QAM.

FrequencyHopping indicates frequency hopping scheme to be applied. Thevalue intraSlot enables ‘Intra-slot frequency hopping’ and the valueinterSlot enables ‘Inter-slot frequency hopping’. If the field isabsent, frequency hopping is not configured.

PUSCH-PowerControl is used to configure UE specific power controlparameter for PUSCH. It consists of p0-AlphaSets field andp0-NominalWithoutGrant field.

P0-AlphaSets field includes a plurality of P0-PUSCH-AlphaSet IEs. AP0-PUSCH-AlphaSet IE comprises a p0-PUSCH-AlphaSetld field and a p0field.

P0 field indicates P0 value for PUSCH with grant (except msg3) in stepsof 1DB. When the field is absent UE applies the value 0.

P0-NominalWithoutGrant field indicates P0 value for UL grant-free PUSCH(configured grant based PUSCH).

PUCCH-ConfigCommon is the cell-specific PUCCH parameter of the initialBWP of the second cell. It consists of subfields such aspucch-ResourceCommon and p0-norminal.

PUCCH-ResourceCommon is an index corresponding to a cell-specific PUCCHresource parameters. One index corresponds to a PUCCH format, a PUCCHtime period, a PUCCH frequency period, a PUCCH code, and the like.

P0-norminal is a power offset applied during PUCCH transmission. Definedas an integer between -202 and 24 in increments of 2. The unit is dBm.

PUCCH-ConfigCommon is used to configure UE specific PUCCH parameters. Itconsists of fields such as dl-DataToUL-ACK field andresourceSetToAddModList field and others.

DL-DataToUL-ACK field includes a list of timing for given PDSCH to theDL ACK.

ResourceSetToAddModList includes a list for adding PUCCH resource sets.

TDD-UL-DL-ConfigurationCommon is cell specific TDD UL/DL configuration.It consists of subfields such as referenceSubcarrierSpacing, pattern1,and pattern2.

ReferenceSubcarrierSpacing is the reference SCS used to determine thetime domain boundary in the UL-DL pattern.

Pattern1 and pattern2 are TDD Uplink Downlink Pattern. It consists ofsubfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots,nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

DL-UL-TransmissionPeriodicity indicates the period of the DL-UL pattern.

NRofDownlinkSlots indicates the number of consecutive full DL slots ineach DL-UL pattern.

NRofDownlinkSymbols indicates the number of consecutive DL symbols fromthe beginning of the slot following the last full DL slot.

NRofUplinkSlots indicates the number of consecutive full UL slots ineach DL-UL pattern.

NR

ofUplinkSymbols indicates the number of consecutive UL symbols at thelast time point of a slot preceding the first full UL slot

UE can be configured with zero or more SR configurations.

Each SR configuration corresponds to one or more logical channels and/orto SCell beam failure recovery and/or to Type7Gap L2 request. Eachlogical channel, SCell beam failure recovery may be mapped to zero orone SR configuration, which is configured by RRC. Type7Gap L2 requestmay be mapped to at least one SR configuration. The SR configuration ofthe logical channel that triggered a BSR or the SCell beam failurerecovery or Type2Gap L2 request is considered as corresponding SRconfiguration for the triggered SR.

A scheduling_request_procedure_for_Type7Gap_L2_request is as follows.

If an SR is triggered by Type7Gap L2 request and there are no other SRspending corresponding to the same SR configuration, the UE/MAC entityshall set the SR_COUNTER of the corresponding SR configuration to 0.

When an SR is triggered, it shall be considered as pending until it iscancelled.

If the SR is triggered by Type7Gap L2 request and a MAC PDU istransmitted and the MAC PDU includes a Type2Gap L2 request, UE cancelthe pending SR and stop the sr-ProhibitTimer.

Only PUCCH resources on a BWP which is active at the time of SRtransmission occasion are considered valid.

If the MAC entity/UE has no valid PUCCH resource configured for thepending SR, UE initiates a Random Access procedure on the SpCell andcancel the pending SR.

If the MAC entity/UE has valid PUCCH resource configured for the pendingSR and if sr-ProhibitTimer is not running at the time of the SRtransmission occasion for SR configured and if the PUCCH resource forthe SR transmission occasion does not overlap with a measurement gap andif SR_COUNTER is smaller than sr-TransMax, UE performs followingactions; UE signal the SR on one valid PUCCH resource for SR and UEincrements SR_COUNTER by 1 and UE starts the sr-ProhibitTimer.

The valid PUCCH resource configured for the SR triggered by Type7Gap L2request is the PUCCH resource on the active UL BWP and associated withthe SR configuration selected for Type7Gap L2 request.

The MAC-CellGroupConfig is used to configure MAC parameters for a cellgroup, including DRX and SR configurations.

The MAC-CellGroupConfig includes a schedulingRequestToAddModList field(List of Scheduling Request configurations to add or modify) and aschedulingRequestToReleaseList field (List of Scheduling Requestconfigurations to release) and a schedulingRequestID-BFR-SCell field(thescheduling request configuration applicable for BFR on SCell) and aschedulingRequestID-Type7GapRequest field(the scheduling requestconfiguration applicable for Type7Gap request.

The schedulingRequestToAddModList field comprises one or moreSchedulingRequestToAddMod IEs.

A SchedulingRequestToAddMod IE comprises following fields:schedulingRequestId, sr-ProhibitTimer (Prohibit timer for SRtransmission on PUCCH), sr-TransMax (Maximum number of SR transmissions)

The schedulingRequestToReleaseList field comprises one or moreschedulingRequestId.

The PUCCH-Config is used to configure UE specific PUCCH parameters (perBWP).

The PUCCH-Config comprises following fields.

A resourceSetToAddModList field (Lists for adding PUCCH resource sets;comprising one or more PUCCH-ResourceSet) and a resourceSetToReleaseListfield (Lists for releasing PUCCH resource sets; comprising one or morePUCCH-ResourceSetId) and a spatialRelationInfoToAddModList field(Configuration of the spatial relation between a reference RS and PUCCH;comprising one or more PUCCH-SpatialRelationInfo) and aspatialRelationInfoToReleaseList field (Lists of spatial relationconfigurations between a reference RS and PUCCH to be released by theUE; comprising one or more PUCCH-SpatialRelationInfold).

A resourceToAddModList field (Lists for adding PUCCH resourcesapplicable for the UL BWP and serving cell in which the PUCCH-Config isdefined; comprising one or more PUCCH-Resource) and aresourceToReleaseList field (Lists for releasing PUCCH resourcesapplicable for the UL BWP and serving cell in which the PUCCH-Config isdefined; comprising one or more PUCCH-ResourceId).

A schedulingRequestResourceToAddModList field (List for addingscheduling request resource for the UL BWP and serving cell in which thePUCCH-Config is defined) and a schedulingRequestResourceToReleaseListfield (List for releasing scheduling request resource for the UL BWP andserving cell in which the PUCCH-Config is defined).

The SchedulingRequestResourceConfig determines physical layer resourceson PUCCH where the UE may send the dedicated scheduling request. ASchedulingRequestResourceConfig is associated with aSchedulingRequestConfig. A SchedulingRequestResourceConfig comprisesfollowing fields.

SchedulingRequestResourceId field (used to identify scheduling requestresources on PUCCH), schedulingRequestID field (The ID of theSchedulingRequestConfig that uses this scheduling request resource),periodicityAndOffset (SR periodicity and offset in number of symbols orslots) and resource (ID of the PUCCH resource in which the UE shall sendthe scheduling request. The actual PUCCH-Resource is configured inPUCCH-Config of the same UL BWP and serving cell as thisSchedulingRequestResourceConfig).

The PUCCH-ResourceSet comprises following fields. A pucch-ResourceSetIdfield and a resourceList field (one or more PUCCH-ResourceId).

The PUCCH-Resource comprises following fields. A pucch-ResourceId field(Identifier of the PUCCH resource), a startingPRB field, a nrofSymbolsfield (the number of symbols used per PUCCH resource) and a nrofPRBsfield (the number of PRBs used per PUCCH resource).

The PUCCH-SpatialRelationInfo is used to configure the spatial settingfor PUCCH transmission and the parameters for PUCCH power control. ThePUCCH-SpatialRelationInfo comprises following fields:pucch-SpatialRelationInfold, servingCellId, referenceSignal andpucch-PathlossReferenceRS-Id.

ServingCellId field indicates the serving cell where the referenceSignalis configured. If this field is absent, UE applies the ServCellId of theserving cell in which this PUCCH-SpatialRelationInfo is configured.

ReferenceSignal field indicates a SSB-Index or a NZP-CSI-RS-ResourceId.

PUCH-PathlossReferenceRS-Id field indicates the pucch-PathlossReferenceRS to be used for PUCCH power control.

A spatial setting for a PUCCH transmission by a UE is provided by aPUCCH-SpatialRelationInfo.

The BFR MAC CE and Truncated BFR MAC CE have a variable size. Theyinclude a bitmap and in ascending order based on the ServCellIndex, beamfailure recovery information i.e. octets containing candidate beamavailability indication (AC) for SCells indicated in the bitmap.

The BFR MAC CE consists of following fields.

SP field indicates beam failure detection for the SpCell of this MACentity. The SP field is set to 1 to indicate that beam failure isdetected for SpCell.

Ci field indicates beam failure detection and the presence of an octetcontaining the AC field for the SCell with ServCellIndex i.

AC field indicates the presence of the Candidate RS ID field in thisoctet. If at least one of the SSBs with SS-RSRP above rsrp-ThresholdBFRamongst the SSBs in candidateBeamRSSCellList or the CSI-RS s withCSI-RSRP above rsrp-ThresholdBFR amongst the CSI-RS s incandidateBeamRSSCellList is available, the AC field is set to 1;otherwise, it is set to 0. If the AC field set to 1, the Candidate RS IDfield is present. If the AC field set to 0, R bits are present instead;

Candidate RS ID field is set to the index of an SSB with SS-RSRP aboversrp-ThresholdBFR amongst the SSBs in candidateBeamRSSCellList or to theindex of a CSI-RS with CSI-RSRP above rsrp-ThresholdBFR amongst theCSI-RSs in candidateBeamRSSCellList. Index of an SSB or CSI-RS is theindex of an entry in candidateBeamRSSCellList corresponding to the SSBor CSI-RS. Index 0 corresponds to the first entry in thecandidateBeamRSSCellList, index 1 corresponds to the second entry in thelist and so on. The length of this field is 6 bits.

A Type7Gap L2 request message is identified by MAC subheader withone-octet eLCID and has a fixed size of one octet. A Type7Gap L2 requestmessage consists of 3 R bits and a A/D field and a MG ID field.

MG ID field contains measGapId2−1. The measGapId2 is the identifier ofthe Type7Gap. The length of the field is 4 bits. A value n in MG IDfield corresponds to a measGapId2 n+1.

A/D field indicates the activation or deactivation of the PositioningMeasurement Gap (i.e., Type7Gap). The field is set to 1 to indicateactivation, otherwise it indicates deactivation. The length of the fieldis 1 bit.

If A/D field is set to 1 and MG ID field is set to n−1, UE requestactivation of type7Gap n.

If A/D field is set to 0 and MG ID field is set to m−1, UE requestdeactivation of type7Gap m.

The subheader of a Type7Gap L2 request message consists of two R bitsand a 6 bit LCID field and a 8 bit eLCID field. The LCID field is set toa first value indicating a 8 bit extended logical channel ID fieldfollows. The first value is 34. If LCID field is set to a second value,a 16 bit extended logical channel ID field follows. UE sets the LCIDfield to the first value for Type7Gap L2 request message. 8 bit eLCIDfield is set to a third value indicating that the type of correspondingMAC CE is type7Gap L2 request message. The third value in eLCID fieldcorresponds to the LCID value calculated from the third value plus aconstant. It is to avoid the ambiguity between LCID value indicated byLCID field and LCID value indicated by eLCID field. The constant is themaximum value of LCID field plus one (i.e.64). For example, if the thirdvalue in eLCID field is 249, it indicates the type of the MAC CEcorresponds to LCID value of 313 (=249+64).

A Type7Gap L2 response message is identified by MAC subheader withone-octet eLCID and has a fixed size. A Type7Gap L2 response messageinclude one or more response information. A response informationincludes a A/D field (n−1) R bits and a measGapld field.

A Type7Gap L2 response message consists of 3 R bits and a A/D field anda MG ID field.

MG ID field contains measGapId2−1. The measGapId2 is the identifier ofthe Type7Gap. The length of the field is 4 bits. A value n in MG IDfield corresponds to a measGapId2 n+1.

A/D field indicates the activation or deactivation of the PositioningMeasurement Gap. The field is set to 1 to indicate activation, otherwiseit indicates deactivation. The length of the field is 1 bit.

If A/D field is set to 1 and MG ID field is set to n−1, GNB commandsactivation of type7Gap n.

If A/D field is set to 0 and MG ID field is set to m−1, GNB commandsdeactivation of type7Gap m.

The subheader of a Type7Gap L2 response message is consists of one R bitand one F field and a LCID field and a 8 bit eLCID field and a L field.The LCID field is set to a first value indicating a 8 bit extendedlogical channel ID field follows. The first value is 34. 8 bit eLCIDfield is set to a fourth value indicating that the type of correspondingMAC CE is type7Gap L2 response message. The fourth value in eLCID fieldcorresponds to the LCID value calculated from the fourth value plus aconstant.

Type7Gap L3 request message includes a measurementIndication field thatcan be set to release or set to setup. If it is set to setup, the fieldincludes a LocationMeasurementInfo IE. The LocationMeasurementInfo IEincludes a dl-PRS-PointA field and RepetitionAndOffset field and aPRS-length field.

DL-PRS-PointA field indicates the absolute radio frequency channelnumber of the carrier for which UE needs to perform PRS measurement.

RepetitionAndOffset field indicates the gap periodicity in ms and offsetin number of subframes of the requested gap.

PRS-length field indicates the gap length of the requested gap.

UE shall set the contents of Type7Gap L3 request message according tothe required gap and trigger BSR to request resource for Type7Gap L3request message. The triggered BSR can trigger SR.

The priority of type7Gap L2 request message is higher than the priorityof type7Gap L3 request message.

The subheader of a Type7Gap L3 request message is consists of one R bitand one F field and a LCID field and a L field. The LDID field is set to1 to indicate that the MAC SDU is SRB1 data.

Type7Gap L3 response message includes a measGapConfig. The measGapConfigmay include a gapConfig1 IE to set up type4Gap corresponding to therequested measurement gap requirements.. The measGapConfig may include agapConfig2 IE to set up type7Gap corresponding to the requestedmeasurement gap requirements. In this case, Type2Gap L2 response messagecan be sent to UE shortly to activate the type7Gap.

PUCCH Spatial Relation Activation/Deactivation MAC CE has followingfields. Serving Cell ID field indicates the identity of the Serving Cellfor which the MAC CE applies. The length of the field is 5 bits;

BWP ID field indicates a UL BWP for which the MAC CE applies. The lengthof the BWP ID field is 2 bits;

PUCCH Resource ID field contains an identifier of the PUCCH resource,which is to be activated with a spatial relation indicated by SpatialRelation Info ID field in the subsequent octet. The length of the fieldis 7 bits.

Spatial Relation Info ID field contains PUCCH-SpatialRelationInfold −1where PUCCH-SpatialRelationInfold is the identifier of the PUCCH SpatialRelation Info in PUCCH-Config in which the PUCCH Resource ID isconfigured. The length of the field is 6 bits;

SCell Activation/Deactivation MAC CE has a fixed size and consists of asingle octet containing seven C-fields.

Ci field indicates the activation/deactivation status of the SCell withSCellIndex i. The Ci field is set to 1 to indicate that the SCell withSCellIndex i shall be activated. The Ci field is set to 0 to indicatethat the SCell with SCellIndex i shall be deactivated;

Logical channels shall be prioritised in accordance with the followingorder (highest priority listed first):

-   -   MAC CE for C-RNTI, or data from UL-CCCH;    -   MAC CE for (Enhanced) BFR;    -   MAC CE for (Extended) BSR, with exception of BSR included for        padding;    -   MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced)        Multiple Entry PHR;    -   MAC CE for Positioning Measurement Gap Activation/Deactivation        Request (Type7Gap L2 request message);    -   data from any Logical Channel (including data from SRB1 and        SRB2), except data from UL-CCCH;    -   MAC CE for BSR included for padding;

When UE receives a DL data transmission (including a MAC CE) from GNB ata first point of time, UE performs relevant action at the time point asfollowing.

If the MAC CE is Type7Gap L2 response message and A/D field is set to 1,UE finishes the activation of a Type7Gap until a second time point1.Alternatively, UE finishes the activation of the Type7Gap at a secondtime point2. Second time point2 is between the first time point and thesecond time point1.

If the MAC CE is Type7Gap L2 response message and A/D field is set to 0,UE finishes the deactivation of a Type7Gap until a second time point1.Alternatively, UE finishes the deactivation of the Type7Gap at a secondtime point2. Second time point2 is between the first time point and thesecond time point1.

Second time point2 is a time point after (the end of) the first timepoint and before (the end of) the second time point1. Second time point2can be equal to the second time point1. Second time point2 cannot beequal to the first time point.

The second time point1 is at first time point+a first variable timeperiod+a first constant time period.

The first variable time period is determined by the timing of DL datatransmission and the corresponding acknowledgement. The first variabletime period is varying depending on TDD UL/DL configuration and a DCIscheduling the DL data transmission.

The first constant time period is applied to ensure UE processing forthe MAC CE. The first constant time period is fixed and common to aplurality of UEs.

If the MAC CE is SCell Activation/Deactivation MAC CE and deactivationof a SCell is indicated by the MAC CE and a type2Gap is to be activatedas a result of SCell deactivation, UE finishes the activation of aType2Gap until a third time point1. Alternatively, UE finishes theactivation of the Type7Gap at a third time point2. The third time point2is between the first time point and the third time point1.

If the MAC CE is SCell Activation/Deactivation MAC CE and deactivationof a SCell is indicated by the MAC CE and a type2Gap is to bedeactivated as a result of SCell deactivation, UE finishes thedeactivation of a Type2Gap until a third time point1. Alternatively, UEfinishes the activation of the Type7Gap at a third time point2. Thethird time point2 is between the first time point and the third timepoint1.

Third time point2 is after (the end of) the first time point and before(the end of) the third time point1. Third time point2 can be equal tothe third time point1. Third time point2 cannot be equal to the firsttime point.

The third time point1 is at first time point+second variable timeperiod+second constant time period.

The second variable time period is determined by the SCell deactivationdelay. SCell deactivation is completed at first time point+secondvariable time period. The second variable time period is varyingdepending on TDD UL/DL configuration and a DCI scheduling the DL datatransmission.

The second constant time period is applied to ensure UE processing forthe MAC CE. The second constant time period is fixed and common to aplurality of UEs. The first constant time period and the second constanttime period can be same or different.

If the MAC CE is PUCCH Spatial Relation Activation/Deactivation MAC CEand a UL spatial relation for a PUCCH resource configured for SRchanges, UE applies the target UL spatial relation at a fourth timepoint.

The fourth time point is at first time point+a first variable timeperiod+a third variable time period (T_(SSB))+a third constant timeperiod

The third variable time period is determined by the periodicity of theSSB configured for L1-RSRP measurement. The third variable time periodis varying depending on the periodicity of SSB in the cell.

The third constant time period is applied to ensure UE processing forthe MAC CE. The third constant time period is fixed and common to aplurality of UEs. The first constant time period and the third constanttime period can be same or different.

If UE receives BWP switching request at DL slot n (or at first timepoint) and the BWP switching results in status change of type2Gap, UEfinishes the activation of a Type2Gap at a fifth time point1.

The fifth time point1 is at first time point+a fourth variable period+afourth constant time period.

The fourth variable period is determined based at least part onbwp-SwitchingDelay and SCS of the BWPs as in table x

The fourth constant time period is to ensure UE processing for type2Gapswitching.

The operations of terminal are listed below.

Terminal receives a RRCReconfiguration message.

The RRCReconfiguration message includes one or more gap configurationinformation and one or more DL BWP configuration information andfirstActiveDownlinkBWP.

Each of one or more gap configuration information includes a measGapIdand a type2Indicator and a gapOffset and a mgl and a mgrp.

Each of one or more DL BWP configuration information includes a bwp-Idand a parameter for bandwidth of BWP and a parameter for SCS of the BWPand a deactivatedMeasGapList.

Terminal determines the active DL BWP based at least in part on thefirstActiveDownlinkBWP-id.

Terminal determines a first gap is to be active based at least in parton deactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList.

Terminal receives a UL grant, the UL grant includes a bandwidth partindicator.

Terminal determines a second gap is to be active based if the second gapis not indicated in a deactivatedMeasGapList of a DL BWP having the samebwp-Id as the bwp-Id indicated in the bandwidth part indicator of the ULgrant.

Terminal activates the second gap at a first point of time, the firstpoint of time is determined based at least in part on a first constantand a first variable, and the first variable is a second constant if theSCS of the BWP is 15 kHz or 30 kHz and is a third constant if the SCS ofthe BWP is 60 kHz or 120 kHz.

The first constant and the second constant and the third constant are 5and 1 and 0.75 respectively.

Terminal receives a RRCReconfiguration message,

The RRCReconfiguration message includes one or more gap configurationinformation and one or more DL BWP configuration information andoptionally firstActiveDownlinkBWP-id and a bwp-InactivityTimer and adefaultDownlinkBWP-Id,

Each of one or more gap configuration information includes a measGapIdand a type2Indicator and a gapOffset and a mgl and a mgrp,

Each of one or more DL BWP configuration information includes a bwp-Idand a parameter for bandwidth of BWP and a parameter for SCS of the BWPand a deactivatedMeasGapList.

Terminal determines the active DL BWP based at least in part on thefirstActiveDownlinkBWP-id

Terminal determines a first gap is to be active based at least in parton a deactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList.

Terminal starts the bwp-InactivityTimer.

Terminal determines a second gap is to be active based at least in parton a deactivatedMeasGapList of a DL BWP associated with thedefaultDownlinkBWP-Id when bwp-InactivityTimer expires.

Terminal activates the second gap at a first point of time, the firstpoint of time is determined based at least in part on a first constantand a first variable, and the first variable is a second constant if theSCS of the BWP is 15 kHz or 30 kHz and is a third constant if the SCS ofthe BWP is 60 kHz or 120 kHz

The first constant and the second constant and the third constant are 5and 1 and 0.75 respectively.

Terminal receives a RRCReconfiguration message, the RRCReconfigurationmessage includes one or more gap configuration information and one ormore SCell configuration information and one or more DL BWPconfiguration information and optionally firstActiveDownlinkBWP-id and abwp-InactivityTimer and a defaultDownlinkBWP-Id, each of one or more gapconfiguration information includes a measGapId and a type2Indicator anda gapOffset and a mgl and a mgrp, each of one or more SCellconfiguration information includes a serving cell index and a servingcell configuration and a sCellDeactivationTimer and adeactivatedMeasGapList2, each of one or more DL BWP configurationinformation includes a bwp-Id and a parameter for bandwidth of BWP and aparameter for SCS of the BWP and a deactivatedMeasGapList.

Terminal determines the active DL BWP based at least in part on thefirstActiveDownlinkBWP-id.

Terminal determines a first gap is to be active based at least in parton deactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList.

Terminal determines to deactivate a SCell.

Terminal determines a second gap is to be active based at least in parton a deactivatedMeasGapList2 of the SCell.

Terminal activates a second gap at a second point of time, the secondpoint of time is determined based at least in part on a first constantand a second variable.

The second variable is determined based at least in part on the timingbetween the first MAC CE transmission and the correspondingacknowledgement if the SCell is deactivated by the first MAC CE.

The second variable is a fourth constant if the SCell is deactivated byexpiry of sCellDeactivationTimer.

The second variable is a fifth constant if the SCell is deactivated by afirst DL RRC message, the first DL RRC message is RRCReconfigurationincluding the configuration of SCell addition.

The first constant and the fourth constant and the fifth constant are 5and 3 and 16 respectively.

Terminal receives a SIB1.

The SIB1 includes a DL BWP configuration information for a initial DLBWP and a UL BWP configuration information for a initial UL BWP.

The UL BWP configuration for the initial UL BWP includes configurationinformation on PRACH occasions.

Terminal receives a RRCReconfiguration message.

The RRCReconfiguration message includes one or more gap configurationinformation and one or more DL BWP configuration information and one ormore UL BWP configuration information and firstActiveDownlinkBWP-id anda bwp-InactivityTimer and a defaultDownlinkBWP-Id.

Each of one or more gap configuration information includes a measGapIdand a type2Indicator and a gapOffset and a mgl and a mgrp.

Each of one or more DL BWP configuration information includes a bwp-Idand a parameter for bandwidth of BWP and a parameter for SCS of the BWPand a deactivatedMeasGapList.

Each of one or more UL BWP configuration information includes a bwp-Idand a parameter for bandwidth of BWP and a parameter for SCS of the BWPand optionally configuration information on PRACH occasions.

Terminal determines the active DL BWP based at least in part on thefirstActiveDownlinkBWP-Id

Terminal determines a first gap is to be active based at least in parton deactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList

Terminal determines PRACH occasions are not configured in the active ULBWP of SpCell based at least in part on one or more UL BWP configurationinformation.

Terminal determines a second gap is to be active based at least in parton the presence of deactivatedMeasGapList of the initial DL BWP ofSpCell

Terminal activates the second gap.

Terminal receives a SIB1.

The SIB1 includes a tdd-UL-DL-ConfigurationCommon

Terminal receives a RRCReconfiguration message, the RRCReconfigurationmessage includes a first gap configuration information or a second gapconfiguration information or both, the first gap configurationinformation includes a musim-GapLength field and amusim-GapRepetitionAndOffset field, the musim-GapLength field indicatesthe length of the gap.

The musim-GapRepetitionAndOffset field indicates the gap repetitionperiod in ms and gap offset in number of subframes and includes ainteger, the integer is chosen from a integer set, the highest value ofthe integer set is equal to the repetition period −1 and the integer isequal to the gap offset.

The second gap configuration information includes gapOffset and a ugland a ugrp

gapOffset indicates the gap offset and ugl indicates the length of thegap and ugrp indicatas the repetition period.

Terminal determines the first subframe of each gap based at least inpart on the integer and the highest value of the integer set if thefirst gap configuration information is included in theRRCReconfiguration

Terminal determines the first slot of each gap based at least in part onthe gapOffset and ugrp and the tdd-UL-DL-ConfigurationCommon if thesecond gap configuration information is included in theRRCReconfiguration

Terminal receives a SIB1

The SIB1 includes a tdd-UL-DL-ConfigurationCommon

Terminal receives a RRCReconfiguration message,

The RRCReconfiguration message includes a second gap configurationinformation or one or more third gap configuration information and oneor more measurement object configuration information.

The second gap configuration information includes gapOffset and a ugland a ugrp

GapOffset indicates the gap offset and ugl indicates the length of thegap and ugrp indicatas the repetition period.

Each of the one or more third gap configuration includes measGapld and agapOffset and a mgl and a mgrp and a mgta.

Terminal determines the first slot of each gap based at least in part onthe gapOffset and ugrp and the tdd-UL-DL-ConfigurationCommon if thesecond gap configuration information is included in theRRCReconfiguration

Terminal determines the first subframe of each gap based at least inpart on the gapOffset and the mgrp and the mgta if one or more third gapconfiguration information is included in the RRCReconfiguration

Terminal performs the second operation group during each gap if thesecond gap configuration information is included in theRRCReconfiguration

The second gap operation group includes performing transmission on PUCCHallocation for SR if SR is triggered and performing transmission onCG-PUSCH resource if configured grant is activated and performingtransmission on PRACH resource if random access procedure is triggeredand not performing SRS transmission at SRS transmission occasions.

Terminal performs the third operation group during each gap if the oneor more third gap configuration information is included in theRRCReconfiguration.

The third gap operation group includes not performing transmission onPUCCH allocation for SR if SR is triggered and not performingtransmission on CG-PUSCH resource if configured grant is activated andperforming transmission on PRACH resource if random access procedure istriggered and not performing SRS transmission at the SRS transmissionoccasions.

Alternatively, Terminal determines the first subframe of each gap basedat least in part on the gapOffset and ugrp if the second gapconfiguration information is included in the RRCReconfiguration anddetermines the first subframe of each gap based at least in part on thegapOffset and the mgrp and the mgta if the third gap configurationinformation is included in the RRCReconfiguration.

The second gap starts at a second slot, the second slot is determinedbased at least in part on the first subframe and thetdd-UL-DL-ConfigurationCommon, the second slot is or is not within thefirst subframe.

The third gap starts at a first slot of the first subframe

Terminal receives a RRCReconfiguration message,

The RRCReconfiguration message includes one or more gap configurationinformation, each of one or more gap configuration information includesa measGapId and a type2Indicator and a gapOffset and a mgl and a mgrp.

Terminal generates a L2 request message or a L3 request message.

Terminal transmits a first MAC PDU that includes the L2 request messageor the L3 request message.

Terminal receives a second MAC PDU that includes a L2 response messageor a L3 response message.

Terminal activates one or more gap based at least in part on the L2response message or on the L3 response message.

The L2 request message includes a measGapld of a gap configurationinformation and the L3 request message includes information for gaplength and gap repetition period and gap offset.

The L2 request message is generated If location measurements towards NRis started and if one or more Type2gap are configured and if at leastone of the type2Gaps meets the measurement gap requirements.

The L3 request message is generated If location measurements towards NRis started and if one or more Type2gaps are configured and if none ofthe type2Gaps meets the measurement gap requirements.

The L2 response message includes one or more measGapld of one or more agap configuration information and the L3 request message includes one ormore gap configuration information.

The L2 response message is received in response to the L2 requestmessage.

The L3 response message is received in response to the L3 requestmessage.

A subheader for the L2 request message in the first MAC PDU consists oftwo reserved bits and a LCID field and eLCID field.

A subheader for the L2 response message in the second MAC PDU consistsof a reserved bit and a F field and a LCID field and eLCID field and a Lfield.

A subheader for the L3 request message in the first MAC PDU and asubheader for the L3 response message in the second MAC PDU consists ofa reserved bit and a F field and a LCID field and a L field.

Terminal receives a RRCReconfiguration message, the RRCReconfigurationmessage includes one or more first gap configuration information and oneor more second gap configuration information, each of one or more firstgap configuration information includes a first identity and atype2Indicator and a gapOffset and a mgl and a mgrp, each of one or moresecond gap configuration information includes a second identity and amusim-GapLength and a musim-GapRepetitionAndOffset.

Terminal generates a L2 request message, the L2 request message includesa third identity.

Terminal transmits a first MAC PDU that includes the L2 request message.

Terminal receives a second MAC PDU that includes a L2 response message,the L2 response message includes a third identity, the third identity inthe L2 request message and the third identity in the L2 response messageare same or different.

Terminal applies one or more first gap based at least in part on thethird identity received in the L2 response message.

The third identity in the L2 request message is one of first identities.

The third identity in the L2 response message is one of firstidentities.

The second gap is applied/used when configured via theRRCReconfiguration message and the first gap is applied/used whenactivated via L2 response message.

Terminal receives a first RRCReconfiguration message, the firstRRCReconfiguration message includes a first configuration related to thereporting of measurement gap requirement information, the firstconfiguration includes a information related to the first gap(type1Gap)requirement reporting and a information related to the secondgap(type4Gap) requirement reporting.

Terminal transmits a UEAssistanceInformation message based at least inpart on the first configuration

Terminal receives a second RRCReconfiguration message, the secondRRCReconfiguration message includes a second configuration, the secondconfiguration includes one or more gap configuration information, thegap configuration information includes a measGapld and a type2Indicatorand a gapOffset and a mgl and a mgrp.

Terminal applies the second configuration in the secondRRCReconfiguration message.

Terminal starts gap operation based at least in part on the one or moregap configuration information in the second configuration.

Terminal initiates RRC re-establishment procedure.

Terminal release the first configuration at a first point of time andthe second configuration at a second point of time.

The first point of time is after the initiation of RRC re-establishmentprocedure and before cell selection.

The second point of time is after receiving RRCReestablishment messagevia SRB1 and before transmitting RRCReestablishmentComplete message viaSRB 1.

Terminal discards a type2Gap L2 request message at a third point of timeand Terminal stops the gap operation at a fourth point of time.

The third point of time is after the initiation of RRC re-establishmentand before the first point of time.

The fourth point of time is after the initiation of RRC re-establishmentprocedure and before discarding any type2Gap L2 request message.

Terminal receives a first RRCReconfiguration message, the firstRRCReconfiguration message includes a first configuration related to thereporting of type5 gap assistance information, the first configurationincludes a prohibit timer field.

Terminal transmits a UEAssistanceInformation message based at least inpart on the first configuration.

Terminal receives a second RRCReconfiguration message, the secondRRCReconfiguration message includes a second configuration, the secondconfiguration includes one or more gap configuration information, thegap configuration information includes a first group of fields or asecond group of fields, the first group of fields includes a musim-gapIdfield and musim-Starting-SFN-AndSubframe field and musim-GapLength fieldand the second group of fields includes a musim-gapId field andmusim-GapRepetitionAndOff set field and musim-GapLength field.

Terminal applies the second configuration in the secondRRCReconfiguration message.

Terminal starts aperiodic gap operation based at least in part on thegap configuration information if the gap configuration informationincludes the first group of fields and periodic gap operation based atleast in part on the gap configuration information if the gapconfiguration information includes the second group of fields.

Terminal initiates RRC re-establishment procedure.

Terminal release the first configuration at a first point of time andthe second configuration at a second point of time.

The first point of time is after the initiation of RRC re-establishmentprocedure and before transmitting RRCReestablishmentRequest message viaSRB0.

The second point of time is after receiving RRCReestablishment messagevia SRB1 and before transmitting RRCReestablishmentComplete message viaSRB1.

Terminal discards a type2Gap L2 request message at a third point of timeand Terminal stops the gap operation at a fourth point of time.

The third point of time is after the initiation of RRC re-establishmentand before the first point of time.

The fourth point of time is after the initiation of RRC re-establishmentprocedure and before discarding any type2Gap L2 request message.

The operations of base station are listed below.

Base station transmits a RRCReconfiguration message.

The RRCReconfiguration message includes one or more gap configurationinformation and one or more DL BWP configuration information andfirstActiveDownlinkBWP.

Each of one or more gap configuration information includes a measGapIdand a type2Indicator and a gapOffset and a mgl and a mgrp.

Each of one or more DL BWP configuration information includes a bwp-Idand a parameter for bandwidth of BWP and a parameter for SCS of the BWPand a deactivatedMeasGapList.

The active DL BWP is determined based at least in part on thefirstActiveDownlinkBWP-id.

A first gap to be active is determined based at least in part ondeactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList.

Base station transmits a UL grant, the UL grant includes a bandwidthpart indicator.

a second gap is to be active if the second gap is not indicated in adeactivatedMeasGapList of a DL BWP having the same bwp-Id as the bwp-Idindicated in the bandwidth part indicator of the UL grant.

The second gap is activated by the terminal at a first point of time,the first point of time is determined based at least in part on a firstconstant and a first variable, and the first variable is a secondconstant if the SCS of the BWP is 15 kHz or 30 kHz and is a thirdconstant if the SCS of the BWP is 60 kHz or 120 kHz

The first constant and the second constant and the third constant are 5and 1 and 0.75 respectively.

Base station transmits a RRCReconfiguration message, theRRCReconfiguration message includes one or more gap configurationinformation and one or more DL BWP configuration information andoptionally firstActiveDownlinkBWP-id and a bwp-InactivityTimer and adefaultDownlinkBWP-Id, each of one or more gap configuration informationincludes a measGapId and a type2Indicator and a gapOffset and a mgl anda mgrp, each of one or more DL BWP configuration information includes abwp-Id and a parameter for bandwidth of BWP and a parameter for SCS ofthe BWP and a deactivatedMeasGapList.

The active DL BWP is determined based at least in part on thefirstActiveDownlinkBWP-id.

A first gap is determined is to be active based at least in part on adeactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList.

Terminal starts the bwp-InactivityTimer.

A second gap to be active is determined at least in part on adeactivatedMeasGapList of a DL BWP associated with thedefaultDownlinkBWP-Id when bwp-InactivityTimer expires.

The second gap is activated by the terminal at a first point of time,the first point of time is determined based at least in part on a firstconstant and a first variable, and the first variable is a secondconstant if the SCS of the BWP is 15 kHz or 30 kHz and is a thirdconstant if the SCS of the BWP is 60 kHz or 120 kHz.

The first constant and the second constant and the third constant are 5and 1 and 0.75 respectively.

Base station transmits a RRCReconfiguration message, theRRCReconfiguration message includes one or more gap configurationinformation and one or more SCell configuration information and one ormore DL BWP configuration information and optionallyfirstActiveDownlinkBWP-id and a bwp-InactivityTimer and adefaultDownlinkBWP-Id, each of one or more gap configuration informationincludes a measGapld and a type2Indicator and a gapOffset and a mgl anda mgrp, each of one or more SCell configuration information includes aserving cell index and a serving cell configuration and asCellDeactivationTimer and a deactivatedMeasGapList2, each of one ormore DL BWP configuration information includes a bwp-Id and a parameterfor bandwidth of BWP and a parameter for SCS of the BWP and adeactivatedMeasGapList.

The active DL BWP is determined based at least in part on thefirstActiveDownlinkBWP-id.

A first gap to be active is determined based at least in part ondeactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList.

Terminal determines to deactivate a SCell.

A second gap to be active is determined least in part on adeactivatedMeasGapList2 of the SCell.

A second gap is activated at a second point of time, the second point oftime is determined based at least in part on a first constant and asecond variable.

The second variable is determined based at least in part on the timingbetween the first MAC CE transmission and the correspondingacknowledgement if the SCell is deactivated by the first MAC CE.

The second variable is a fourth constant if the SCell is deactivated byexpiry of sCellDeactivationTimer.

The second variable is a fifth constant if the SCell is deactivated by afirst DL RRC message, the first DL RRC message is RRCReconfigurationincluding the configuration of SCell addition.

The first constant and the fourth constant and the fifth constant are 5and 3 and 16 respectively.

Base station transmits a SIB1.

The SIB1 includes a DL BWP configuration information for a initial DLBWP and a UL BWP configuration information for a initial UL BWP.

The UL BWP configuration for the initial UL BWP includes configurationinformation on PRACH occasions.

Base station transmits a RRCReconfiguration message.

The RRCReconfiguration message includes one or more gap configurationinformation and one or more DL BWP configuration information and one ormore UL BWP configuration information and firstActiveDownlinkBWP-id anda bwp-InactivityTimer and a defaultDownlinkBWP-Id.

Each of one or more gap configuration information includes a measGapIdand a type2Indicator and a gapOffset and a mgl and a mgrp.

Each of one or more DL BWP configuration information includes a bwp-Idand a parameter for bandwidth of BWP and a parameter for SCS of the BWPand a deactivatedMeasGapList.

Each of one or more UL BWP configuration information includes a bwp-Idand a parameter for bandwidth of BWP and a parameter for SCS of the BWPand optionally configuration information on PRACH occasions.

The active DL BWP is determined based at least in part on thefirstActiveDownlinkBWP-Id.

A first gap to be active is determined based at least in part ondeactivatedMeasGapList of the active DL BWP if the first gap is notindicated in the deactivatedMeasGapList.

Terminal determines PRACH occasions are not configured in the active ULBWP of SpCell based at least in part on one or more UL BWP configurationinformation.

A second gap to be active is determined least in part on the presence ofdeactivatedMeasGapList of the initial DL BWP of SpCell.

Base station transmits a SIB1

The SIB1 includes a tdd-UL-DL-ConfigurationCommon

Base station transmits a RRCReconfiguration message, theRRCReconfiguration message includes a first gap configurationinformation or a second gap configuration information or both, the firstgap configuration information includes a musim-GapLength field and amusim-GapRepetitionAndOffset field, the musim-GapLength field indicatesthe length of the gap.

The musim-GapRepetitionAndOffset field indicates the gap repetitionperiod in ms and gap offset in number of subframes and includes ainteger, the integer is chosen from a integer set, the highest value ofthe integer set is equal to the repetition period −1 and the integer isequal to the gap offset.

The second gap configuration information includes gapOffset and a ugland a ugrp.

gapOffset indicates the gap offset and ugl indicates the length of thegap and ugrp indicatas the repetition period.

The first subframe of each gap is determined based at least in part onthe integer and the highest value of the integer set if the first gapconfiguration information is included in the RRCReconfiguration.

The first slot of each gap is determined based at least in part on thegapOffset and ugrp and the tdd-UL-DL-ConfigurationCommon if the secondgap configuration information is included in the RRCReconfiguration.

Base station transmits a SIB1

The SIB1 includes a tdd-UL-DL-ConfigurationCommon

Base station transmits a RRCReconfiguration message, theRRCReconfiguration message includes a second gap configurationinformation or one or more third gap configuration information and oneor more measurement object configuration information, the second gapconfiguration information includes gapOffset and a ugl and a ugrp.

GapOffset indicates the gap offset and ugl indicates the length of thegap and ugrp indicatas the repetition period.

Each of the one or more third gap configuration includes measGapId and agapOffset and a mgl and a mgrp and a mgta.

The first slot of each gap is determined based at least in part on thegapOffset and ugrp and the tdd-UL-DL-ConfigurationCommon if the secondgap configuration information is included in the RRCReconfiguration.

The first subframe of each gap is determined based at least in part onthe gapOffset and the mgrp and the mgta if one or more third gapconfiguration information is included in the RRCReconfiguration.

The second operation group is performed during each gap if the secondgap configuration information is included in the RRCReconfiguration.

The second gap operation group includes performing transmission on PUCCHallocation for SR if SR is triggered and performing transmission onCG-PUSCH resource if configured grant is activated and performingtransmission on PRACH resource if random access procedure is triggeredand not performing SRS transmission at SRS transmission occasions.

The third operation group is performed during each gap if the one ormore third gap configuration information is included in theRRCReconfiguration.

The third gap operation group includes not performing transmission onPUCCH allocation for SR if SR is triggered and not performingtransmission on CG-PUSCH resource if configured grant is activated andperforming transmission on PRACH resource if random access procedure istriggered and not performing SRS transmission at the SRS transmissionoccasions.

Alternatively, the first subframe of each gap is determined based atleast in part on the gapOffset and ugrp if the second gap configurationinformation is included in the RRCReconfiguration and determines thefirst subframe of each gap based at least in part on the gapOffset andthe mgrp and the mgta if the third gap configuration information isincluded in the RRCReconfiguration.

The second gap starts at a second slot, the second slot is determinedbased at least in part on the first subframe and thetdd-UL-DL-ConfigurationCommon, the second slot is or is not within thefirst subframe.

The third gap starts at a first slot of the first subframe.

Base station transmits a RRCReconfiguration message, theRRCReconfiguration message includes one or more gap configurationinformation, each of one or more gap configuration information includesa measGapld and a type2Indicator and a gapOffset and a mgl and a mgrp.

A L2 request message or a L3 request message is generated by theterminal.

Base station receives a first MAC PDU that includes the L2 requestmessage or the L3 request message.

Base station transmits a second MAC PDU that includes a L2 responsemessage or a L3 response message.

One or more gap are activated based at least in part on the L2 responsemessage or on the L3 response message.

The L2 request message includes a measGapld of a gap configurationinformation and the L3 request message includes information for gaplength and gap repetition period and gap offset

The L2 request message is generated If location measurements towards NRis started and if one or more Type2gaps are configured and if at leastone of the type2Gaps meets the measurement gap requirements

The L3 request message is generated If location measurements towards NRis started and if one or more Type2gaps are configured and if none ofthe type2Gaps meets the measurement gap requirements

The L2 response message includes one or more measGapld of one or more agap configuration information and the L3 request message includes one ormore gap configuration information

The L2 response message is received in response to the L2 requestmessage.

The L3 response message is received in response to the L3 requestmessage.

A subheader for the L2 request message in the first MAC PDU consists oftwo reserved bits and a LCID field and eLCID field.

A subheader for the L2 response message in the second MAC PDU consistsof a reserved bit and a F field and a LCID field and eLCID field and a Lfield.

A subheader for the L3 request message in the first MAC PDU and asubheader for the L3 response message in the second MAC PDU consists ofa reserved bit and a F field and a LCID field and a L field.

Base station transmits a RRCReconfiguration message, theRRCReconfiguration message includes one or more first gap configurationinformation and one or more second gap configuration information, eachof one or more first gap configuration information includes a firstidentity and a type2Indicator and a gapOffset and a mgl and a mgrp, eachof one or more second gap configuration information includes a secondidentity and a musim-GapLength and a musim-GapRepetitionAndOffset.

Terminal a L2 request message is generated, the L2 request messageincludes a third identity.

Base station receives a first MAC PDU that includes the L2 requestmessage.

Base station transmits a second MAC PDU that includes a L2 responsemessage, the L2 response message includes a third identity, the thirdidentity in the L2 request message and the third identity in the L2response message are same or different.

One or more first gap are applied based at least in part on the thirdidentity received in the L2 response message.

The third identity in the L2 request message is one of first identities.

The third identity in the L2 response message is one of firstidentities.

The second gap is applied/used when configured via theRRCReconfiguration message and the first gap is applied/used whenactivated via L2 response message.

Base station transmits a first RRCReconfiguration message, the firstRRCReconfiguration message includes a first configuration related to thereporting of measurement gap requirement information, the firstconfiguration includes a information related to the first gap(type1Gap)requirement reporting and a information related to the secondgap(type4Gap) requirement reporting.

Base station receives a UEAssistanceInformation message based at leastin part on the first configuration

Base station transmits a second RRCReconfiguration message, the secondRRCReconfiguration message includes a second configuration, the secondconfiguration includes one or more gap configuration information, thegap configuration information includes a measGapId and a type2Indicatorand a gapOffset and a mgl and a mgrp, the second configuration in thesecond RRCReconfiguration message is applied.

Gap operation is started based at least in part on the one or more gapconfiguration information in the second configuration.

RRC re-establishment procedure is initiated.

The first configuration is released at a first point of time and thesecond configuration at a second point of time.

The first point of time is after the initiation of RRC re-establishmentprocedure and before cell selection.

The second point of time is after receiving RRCReestablishment messagevia SRB1 and before transmitting RRCReestablishmentComplete message viaSRB1.

A type2Gap L2 request message is discarded at a third point of time andterminal stops the gap operation at a fourth point of time.

The third point of time is after the initiation of RRC re-establishmentand before the first point of time.

The fourth point of time is after the initiation of RRC re-establishmentprocedure and before discarding any type2Gap L2 request message.

Base station transmits a first RRCReconfiguration message, the firstRRCReconfiguration message includes a first configuration related to thereporting of type5 gap assistance information, the first configurationincludes a prohibit timer field.

Base station receives a UEAssistanceInformation message based at leastin part on the first configuration.

Base station transmits a second RRCReconfiguration message, the secondRRCReconfiguration message includes a second configuration, the secondconfiguration includes one or more gap configuration information, thegap configuration information includes a first group of fields or asecond group of fields, the first group of fields includes a musim-gapIdfield and musim-Starting-SFN-AndSubframe field and musim-GapLength fieldand the second group of fields includes a musim-gapId field andmusim-GapRepetitionAndOff set field and musim-GapLength field.

The second configuration in the second RRCReconfiguration message isapplied.

Terminal starts aperiodic gap operation based at least in part on thegap configuration information if the gap configuration informationincludes the first group of fields and periodic gap operation based atleast in part on the gap configuration information if the gapconfiguration information includes the second group of fields.

RRC re-establishment procedure is initiated.

The first configuration is released at a first point of time and thesecond configuration at a second point of time.

The first point of time is after the initiation of RRC re-establishmentprocedure and before transmitting RRCReestablishmentRequest message viaSRB0.

The second point of time is after receiving RRCReestablishment messagevia SRB1 and before transmitting RRCReestablishmentComplete message viaSRB1.

A type2Gap L2 request message is discarded at a third point of time andterminal stops the gap operation at a fourth point of time.

The third point of time is after the initiation of RRC re-establishmentand before the first point of time.

The fourth point of time is after the initiation of RRC re-establishmentprocedure and before discarding any type2Gap L2 request message.

The terminal is configured with h SR configurations and j SR resourceconfigurations and k PUCCH resource configurations and m serving cellsand n UL BWPs. h and j and k are integers equal to or greater than zero.m and n are integers equal to or greater than one. h and j and k and mand n can be different from or equal to each other.

Each of h SR configurations consists of an identifier 1(SchedulingRequestId) and a first timer value (sr-ProhibitTimer) and afirst counter value (sr-TransMax).

Each of h SR configurations is applied to the terminal in one or more ULBWPs. Each of j SR resource configurations is applied to the terminal inan UL BWP associated with the SR resource configuration. Each of k PUCCHresource configurations is applied to the terminal in an UL BWPassociated with the PUCCH resource configuration.

The one or more UL BWP is the SpCell's UL BWP for which at least one SRresource configuration is configured.

The UL BWP associated with a SR resource configuration is the UL BWP forwhich the SR resource configuration is configured.

The UL BWP associated with PUCCH resource configuration is the UL BWPfor which the PUCCH resource configuration is configured.

Each of m SR resource configurations consists of an identifier2(schedulingRequestResourceId) and an identifier1 (SchedulingRequestId)and an identifier3 (pucch-ResourceId) and a parameter representingperiodicity and offset in number of symbols or slots.

A SR resource configuration and a SR configuration are associated witheach other if they have a same identifier 1.

A SR configuration is associated with a PUCCH resource configuration ifthe PUCCH resource configuration is indicated in the associated SRresource configuration.

A CellGroupConfig includes a mac-CellGroupConfig and one or moreServingCellConfig.

A ServingCellConfig includes one or more BWP-UplinkDedicated.

A SR configuration is included in mac-CellGroupConfig inCellGroupConfig.

A PUCCH-Config is included in a BWP-UplinkDedicated.

A PUCCH-Config includes zero or more SR resource configurations and zeroor more PUCCH-Resource configurations.

A SR resource configuration is included in a PUCCH-Config in aBWP-UplinkDedicated in a ServingCellConfig in a CellGroupConfig.

A PUCCH-resource configuration is included in a PUCCH-Config in aBWP-UplinkDedicated in a ServingCellConfig in a CellGroupConfig.

Terminal transmits a SR on PUCCH resource determined based at least inpart on the identifier 1 and the identifier2 and the identifier3.

The terminal triggers a Scheduling Request for a second UL MAC CE(type7Gap L2 request message) if the second UL MAC CE (type7Gap L2request message) has been triggered and not cancelled and UL-SCHresources are not sufficient to accommodate the second UL MAC CE(type7Gap L2 request message) plus subheader.

The terminal triggers a Scheduling Request for a second UL MAC CE(type7Gap L2 request message) if the second UL MAC CE (type7Gap L2request message) has been triggered and not cancelled and UL-SCHresources are not available for a new transmission.

The terminal signals the scheduling request on a first PUCCH resource ifa sr-ProhibitTimer is not running and SR_COUNTER is smaller than asr-TransMax and the Scheduling Request for the second UL MAC CE(type7Gap L2 request message) is pending.

An SR is considered pending after it is triggered and before it iscancelled.

The sr-ProhibitTimer and the sr-TransMax and the first PUCCH resourceare determined based on a first SR configuration and a first SR resourceconfiguration.

The first SR configuration is indicated by aschedulingRequestID-Type7GapReq field in a mac-CellGroupConfig IE if theschedulingRequestID-Type7GapReq field is included in amac-CellGroupConfig IE.

The first SR configuration is one of a first SR configuration group (orthe first SR configuration is any SR configuration of the first SRconfiguration group; the first SR configuration is any SR configurationvalid in the currently active UL BWP of SpCell) if theschedulingRequestID-Type7GapReq field is not included in amac-CellGroupConfig IE.

The first SR configuration group comprises SR configurations associatedwith the currently active UL BWP of a SpCell.

A SR configuration is associated with an UL BWP if an associated SRresource configuration is configured for the UL BWP.

A SR resource configuration associated with a SR configuration is the SRresource configuration configured with the same identifier1 as the SRresource configuration.

A SR configuration is valid in a UL BWP if an associated SR resourceconfiguration is configured for the UL BWP.

The terminal signals the scheduling request on a first PUCCH resourcewith a spatial setting provided by a first PUCCH-SpatialRelationlnfo ifa sr-ProhibitTimer is not running and SR_COUNTER is smaller than asr-TransMax and the Scheduling Request for the second UL MAC CE(type7Gap L2 request message) is pending.

The first PUCCH-SpatialRelationInfo is indicated by a PUCCH SpatialRelation Activation/Deactivation MAC CE. The PUCCH Spatial RelationActivation/Deactivation MAC CE comprises a Serving Cell ID field settingto the ServCellIndex of the SpCell and a BWP ID field setting to thebwp-Id of the currently active UL BWP and the PUCCH Resource ID fieldsetting to the identifier3 of the first PUCCH resource and a SpatialRelation Info ID containing a PUCCH-SpatialRelationInfold −1. ThePUCCHSpatialRelationInfold corresponds to the firstPUCCH-SpatialRelationInfo.

The terminal determines that a type7Gap with a measGapId2 equal to n issufficient for performing location measurements towards NR.

The terminal transmits to the base station a first MAC PDUcontaining/including a type7Gap L2 request message. The Type7Gap L2request message includes a A/D field and a MG ID field.

The MG ID field is set to −1. The A/D field is set to 1.

The terminal starts to perform location measurements toward NR

The terminal generates, based on the result of logical channelprioritization, a MAC subPDU requesting activation of a measurement gapfor positioning.

The terminal includes the MAC subPDU in a MAC PDU.

The terminal transmits to the base station the MAC PDU.

The MAC subPDU includes a type7Gap request L2 message if type7Gaps areconfigured and at least one of type7Gap is sufficient for the locationmeasurement.

The MAC subPDU includes a type7Gap request L3 message if type7Gap is notconfigured.

The priority of the type7Gap request L2 message is higher than thepriority of the type7Gap request L3 message.

MAC subheader of the MAC subPDU including the type7Gap request L2message consists of a first LCID field and a second LCID field.

MAC subheader of the MAC subPDU including the type7Gap request L3message consists of a first LCID field and a L field.

The MAC subPDU including the type7Gap request L2 message include ainformation representing a measurement gap for positioning referencesignal measurement The MAC subPDU including the type7Gap request L2message include a information representing a positioning referencesignal

The terminal triggers a scheduling request for either transmitting afirst MAC CE or a second MAC CE.

The terminal transmits a SR according to a first SR configuration or asecond SR configuration.

The terminal receives an UL grant for new transmission.

The terminal determines whether to allocate resource for the MAC CEbased at least in part on the priority of the MAC CE.

The terminal transmits a MAC PDU.

The first SR configuration is indicated by a SR configuration identifierin a MAC-CellGroupConfig. The first SR configuration is used if thefirst MAC CE triggers the scheduling request.

The second SR configuration is any SR configurations of theMAC-CellGroupConfig.

The second SR configuration is any SR configuration among SRconfigurations configured in the MAC-CellGroup-Config.

A priority of the first MAC CE is higher than a priority of the secondMAC CE.

MAC subheader of the MAC subPDU including the second MAC CE consists ofa first LCID field and a second LCID field.

MAC subheader of the MAC subPDU including the first MAC CE consists of afirst LCID field and a L field.

The First MAC CE is BFR MAC CE.

The Second MAC CE is type7Gap L2 request message.

The terminal receives a MAC PDU including a MAC subPDU at a first pointof time. The MAC subPDU comprises a MAC subheader and a Type7Gap L2response message.

The Type7Gap L2 response message includes a A/D field and a MG ID field.

The terminal finishes the activation of a Type7Gap until a second pointof time if the A/D field is set to 1

MeasGapId2 of the Type7Gap to be activated is equal to the first valueplus one. The first value is indicated in the MG ID field.

The second point of time is determined based at least in part on thefirst point of time and the first variable time period (T_HARQ) and asecond constant time period (x ms).

The first variable time period is determined by the timing of the DLdata transmission and the acknowledgement. The DL data contains the MACPDU. The acknowledgement is a positive acknowledgement for the DL data.

The second constant time period is fixed and common to a plurality ofterminals.

The terminal receives a MAC PDU including a MAC subPDU at a first pointof time. The MAC subPDU comprises a MAC subheader and a informationresulting in measurement gap activation.

The terminal finishes the activation of the measurement gap until asecond point of time if the information resulting in measurement gapactivation is a Type7Gap L2 request.

The second point of time is determined based at least in part on thefirst point of time and the first variable time period (T_HARQ) and afirst constant time period (x ms).

The first variable time period is determined by the timing of the DLdata transmission and the acknowledgement. The DL data contains the MACPDU. The acknowledgement is a positive acknowledgement for the DL data.

The first constant time period is fixed and common for a plurality ofterminals.

The terminal finishes the activation of the measurement gap until athird point of time if the information resulting in measurement gapactivation is a SCell activation request.

The third point of time is determined based at least in part on thefourth point of time and the second constant time period.

The fourth point of time is when a first SCell activation is completed.The first SCell is associated with the measurement gap. determined basedon type2GapStatus2.

The terminal transmits to the base station a UECapabilityInformation.The UECapabilityInformation includes a Type7GapInfo2 indicating supportof low latency measurement gap activation request and a Type7GapInfo1indicating support of low latency measurement gap activation.

The terminal transmits to the LMF a ProvideCapabilities. TheProvideCapabilities includes a Type7GapInfo3 indicating support of lowlatency measurement gap activation.

FIG. 3 is a flow diagram illustrating an operation of a terminal.

In 3a-05, UE transmits to the base station via SRB1 aUECapabilityInformation. The UECapabilityInformation includes aType7GapInfo2 indicating support of low latency measurement gapactivation request and a Type7GapInfo1 indicating support of low latencymeasurement gap activation.

In 3a-10, UE transmits to the LMF via SRB2 a ProvideCapabilities. TheProvideCapabilities includes a Type7GapInfo3 indicating support of lowlatency measurement gap activation.

In 3a-15, UE receives from the base station a RRCReconfiguration. TheRRCReconfiguration includes a MAC-CellGroupConfig IE and one or morePUCCH-Config IEs and a MeasGapConfig IE.

In 3a-20, UE sets up measurement gaps and activates some of them.

In 3a-25, UE performs Gap operation during the activated gaps.

In 3a-30, UE starts to perform location measurements toward NR.

UE generates a MAC subPDU requesting activation of a measurement gap forpositioning based on the result of logical channel prioritization.

In 3a-35, UE transmits Type7Gap L2 request message or Type7Gap L3request message.

In 3a-40, UE receives Type7Gap L2 response message or Type7Gap L3response in response to the Type2Gap L2 request message the Type3Gap L3request message.

In 3a-45, UE activates measurement gaps in accordance with the receivedmessage.

In 3a-50, UE performs Gap operation.

FIG. 4A is a block diagram illustrating the internal structure of a UEto which the disclosure is applied.

Referring to the diagram, the UE includes a controller 4A-01, a storageunit 4A-02, a transceiver 4A-03, a main processor 4A-04 and I/O unit4A-05.

The controller 4A-01 controls the overall operations of the UE in termsof mobile communication. For example, the controller 4A-01receives/transmits signals through the transceiver 4A-03. In addition,the controller 4A-01 records and reads data in the storage unit 4A-02.To this end, the controller 4A-01 includes at least one processor. Forexample, the controller 4A-01 may include a communication processor (CP)that performs control for communication and an application processor(AP) that controls the upper layer, such as an application program. Thecontroller controls storage unit and transceiver such that UE operationsillustrated in FIG. 2 and FIG. 3 are performed.

The storage unit 4A-02 stores data for operation of the UE, such as abasic program, an application program, and configuration information.The storage unit 4A-02 provides stored data at a request of thecontroller 4A-01.

The transceiver 4A-03 consists of a RF processor, a baseband processorand one or more antennas. The RF processor performs functions fortransmitting/receiving signals through a wireless channel, such assignal band conversion, amplification, and the like. Specifically, theRF processor up-converts a baseband signal provided from the basebandprocessor into an RF band signal, transmits the same through an antenna,and down-converts an RF band signal received through the antenna into abaseband signal. The RF processor may include a transmission filter, areception filter, an amplifier, a mil0r, an oscillator, adigital-to-analog converter (DAC), an analog-to-digital converter (ADC),and the like. The RF processor may perform MIMO and may receive multiplelayers when performing the MIMO operation. The baseband processorperforms a function of conversion between a baseband signal and a bitstring according to the physical layer specification of the system. Forexample, during data transmission, the baseband processor encodes andmodulates a transmission bit string, thereby generating complex symbols.In addition, during data reception, the baseband processor demodulatesand decodes a baseband signal provided from the RF processor, therebyrestoring a reception bit string.

The main processor 4A-04 controls the overall operations other thanmobile operation. The main processor 4A-04 process user input receivedfrom I/O unit 4A-05, stores data in the storage unit 4A-02, controls thecontroller 4A-01 for required mobile communication operations andforward user data to I/O unit 4A-05.

I/O unit 4A-05 consists of equipment for inputting user data and foroutputting user data such as a microphone and a screen. I/O unit 4A-05performs inputting and outputting user data based on the mainprocessor's instruction.

FIG. 4B is a block diagram illustrating the configuration of a basestation according to the disclosure.

As illustrated in the diagram, the base station includes a controller4B-01, a storage unit 4B-02, a transceiver 4B-03 and a backhaulinterface unit 4B-04.

The controller 4B-01 controls the overall operations of the main basestation. For example, the controller 4B-01 receives/transmits signalsthrough the transceiver 4B-03, or through the backhaul interface unit4B-04. In addition, the controller 4B-01 records and reads data in thestorage unit 4B-02. To this end, the controller 4B-01 may include atleast one processor. The controller controls transceiver, storage unitand backhaul interface such that base station operation illustrated inFIG. 2 are performed.

The storage unit 4B-02 stores data for operation of the main basestation, such as a basic program, an application program, andconfiguration information. Particularly, the storage unit 4B-02 maystore information regarding a bearer allocated to an accessed UE, ameasurement result reported from the accessed UE, and the like. Inaddition, the storage unit 4B-02 may store information serving as acriterion to deter mine whether to provide the UE with multi-connectionor to discontinue the same. In addition, the storage unit 4B -02provides stored data at a request of the controller 4B -01.

The transceiver 4B-03 consists of a RF processor, a baseband processorand one or more antennas. The RF processor performs functions fortransmitting receiving signals through a wireless channel, such assignal band conversion, amplification, and the like. Specifically, theRF processor up-converts a baseband signal provided from the basebandprocessor into an RF band signal, transmits the same through an antenna,and down -converts an RF band signal received through the antenna into abaseband signal. The RF processor may include a transmission filter, areception filter, an amplifier, a mi10r, an oscillator, a DAC, an ADC,and the like. The RF processor may perform a down link MIMO operation bytransmitting at least one layer. The baseband processor performs afunction of conversion between a baseband signal and a bit stringaccording to the physical layer specification of the first radio accesstechnology. For example, during data transmission, the basebandprocessor encodes and modulates a transmission bit string, therebygenerating complex symbols. In addition, during data reception, thebaseband processor demodulates and decodes a baseband signal providedfrom the RF processor, thereby restoring a reception bit string.

The backhaul interface unit 4B-04 provides an interface forcommunicating with other nodes inside the network. The backhaulinterface unit 4B -04 converts a bit string transmitted from the basestation to another node, for example, another base station or a corenetwork, into a physical signal, and converts a physical signal receivedfrom the other node into a bit string.

What is claimed is:
 1. A method by a terminal, the method comprising:receiving, by the terminal from a base station, a RRCReconfiguration,the RRCReconfiguration includes one or more gap configuration and aMAC-CellGroupConfig and one or more uplink bandwidth part configuration,each of the one or more gap configuration includes an identifier of thegap, the MAC-CellGroupConfig includes a first identifier1 and one ormore first configuration, each of the one or more first configurationincludes an identifier1 and a value for a prohibit timer and an integerfor a counter, each of the one or more uplink bandwidth partconfiguration includes one or more second configurations, each of theone or more second configurations includes the identifier1 and anidentifier2 and a parameter indicating periodicity and offset, theidentifier2 is an identifier of each of the one or more secondconfigurations; triggering, by the terminal, a Scheduling Request for afirst Medium Access Control (MAC) Control Element (CE) if the first MACCE has been triggered and not cancelled and if uplink shared channelresources are not available for a new transmission; performing, by theterminal, Scheduling Request transmission based on a specific firstconfiguration and a specific second configuration; and transmitting, bythe terminal to the base station to request activation of a first gap,the first MAC CE, wherein the specific first configuration is the firstconfiguration corresponding to the first identifier1 and the specificsecond configuration is the second configuration associated with thespecific first configuration.
 2. The method of claim 1, wherein thefirst MAC CE includes a second field, the second field includes a valuecorresponding to an identifier of the first gap for which activation isrequested.
 3. The method of claim 2, wherein the gap having theidentifier of the gap equal to the value indicated in the second fieldplus one is requested to be activated.
 4. The method of claim 1, whereinthe first configuration is associated with the second configuration ifthe identifier1 of the first configuration is included in the secondconfiguration.
 5. A terminal in a wireless communication system, theterminal comprising: a transceiver configured to transmit and receive asignal; and a controller configured to control the transceiver to:receive from a base station a RRCReconfiguration, the RRCReconfigurationincludes one or more gap configuration and a MAC-CellGroupConfig and oneor more uplink bandwidth part configuration, each of the one or more gapconfiguration includes an identifier of the gap, the MAC-CellGroupConfigincludes a first identifier1 and one or more first configuration, eachof the one or more first configuration includes an identifier1 and avalue for a prohibit timer and an integer for a counter, each of the oneor more uplink bandwidth part configuration includes one or more secondconfigurations, each of the one or more second configurations includesthe identifier1 and an identifier2 and a parameter indicatingperiodicity and offset, the identifier2 is an identifier of each of theone or more second configurations; trigger a Scheduling Request for afirst Medium Access Control (MAC) Control Element (CE) if the first MACCE has been triggered and not cancelled and if uplink shared channelresources are not available for a new transmission perform SchedulingRequest transmission based on a specific first configuration and aspecific second configuration; and transmit to the base station torequest activation of a first gap, the first MAC CE, wherein thespecific first configuration is the first configuration corresponding tothe first identifier1 and the specific second configuration is thesecond configuration associated with the specific first configuration.6. A method by a base station, the method comprising: transmitting, bythe base station to a terminal, a RRCReconfiguration, theRRCReconfiguration includes one or more gap configuration and aMAC-CellGroupConfig and one or more uplink bandwidth part configuration,each of the one or more gap configuration includes an identifier of thegap, the MAC-CellGroupConfig includes a first identifier1 and one ormore first configuration, each of the one or more first configurationincludes an identifier1 and a value for a prohibit timer and an integerfor a counter, each of the one or more uplink bandwidth partconfiguration includes one or more second configurations, each of theone or more second configurations includes the identifier1 and anidentifier2 and a parameter indicating periodicity and offset, theidentifier2 is an identifier of each of the one or more secondconfigurations; performing, by the base station, Scheduling Requestreception from the terminal based on a specific first configuration anda specific second configuration; and receiving, by the base station fromthe terminal, a first Medium Access Control (MAC) Control Element (CE)related to activation request of a first gap, wherein the specific firstconfiguration is the first configuration corresponding to the firstidentifier1 and the specific second configuration is the secondconfiguration associated with the specific first configuration.